[Feature]: Preparation for future lint Rstest support

[elecmonkey]

What problem does this feature solve?

Related discussion: web-infra-dev/rstest#85 (comment)

Most of the rules for jest may also be applicable to Rstest. In a typical repo which using Rstest - web-infra-dev/rsbuild - around 2/3 of the eslint-plugin-jest rules can pass directly.

So I have a proposal: we could share an abstraction layer under both Jest and Rstest lint rules in our repo. Consider Rslint is now porting rules from eslint-plugin-jest actively, we can extract some utils outside first. once the jest rules become stable, we can start building Rstest rules on top of the existing things.

@fansenze @eryue0220

What does the proposed API of configuration look like?

some idea: maybe we could go on use in jest's rules in internal/plugins/jest/rules/*/*.go:

utils.ParseJestFnCall(node, ctx)

internally, that can become a wrapper for the new layer:

testfw.ParseFnCall(node, ctx, testfw.JestProfile)

[eryue0220]

I think this proposal is great and feasible, but the first step is what kind of rules is rstest need then we can move the common rules to the shared or some directory that can share.

As for the API design I'm not sure it's need to add a new abstract parser layer for jest and rstest, according to the oxc codebase for jest and vitest, ParseJestFnCall is enough. But I'm not very familiar with rstest, and this is just my initial thought.