feat: Add parameterization rule logic

[e-fisher]

Description

This is the first PR of parameterization rule implementation, includes rule logic, unit tests, and a refactor of how we currently apply rules.

Refactor rule application:

Some rules need to have a state to keep track of extracted value, requests matched and sequential variable IDs. Currently, it was done by using correlationState object, which was passed as argument when applying rules. Parameterization rule required a state to keep track of replaced requests and, while similar to correlation state, it didn't require all its properties.

To address this, I've introduced Rule instances with the following structure:

export interface RuleInstance {
  apply: (request: RequestSnippetSchema) => RequestSnippetSchema
  rule: TestRule
  state: CorrelationState | ParameterizationState | other 
}

This allowed to encapsulate state inside rule instance, reduce coupling because consumers applying rules no longer need to know about rule's state.

How to Test

1. Verify correlation and other existing rules still works as expected.
2. The parameterization rule could be tested by manually adding rules to the generator, but it will be easier to do in the follow PR which adds UI

Checklist

• I have performed a self-review of my code.
• I have added tests for my changes.
• I have run linter locally (npm run lint) and all checks pass.
• I have run tests locally (npm test) and all tests pass.
• I have commented on my code, particularly in hard-to-understand areas.

Screenshots (if appropriate):

Related PR(s)/Issue(s)

[e-fisher]

I've moved inline tests to codegen.test.ts because of:

1. Keep all tests related to codegen in one place
2. test:watch would skip codegen.test.ts on change because of inline tests presence

[going-confetti]

Looks good! I like the improvements 👍

[Llandy3d]

Looks great 🙌
Minor comments and I really like the instance concept 🚀

[Llandy3d]

should this be different for each instance ?
I think initially it was a single object shared between all rules to not have them generate the same id 🤔

[e-fisher]

Good catch! Moved generator initialization up and added tests to verify ID generation

[Llandy3d]

nit: wouldn't it make it more readable to have the function defined separately and just pass the name here ? 🤔

[Llandy3d]

🚀