fix replace resolver persistence

[EmrysMyrddin]

Description

This PR aims to fix the feature allowing to replace the resolver function in place just before it is called.

Since the onResolverCalled hook is being called on each resolver calls, it is expected that the replaceResolverFn function only applies to this resolver call. This PR implement this behaviour.

Fixes #1524

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Since this is changing the behaviour of replaceResolverFn, it possible that it introduce some unexpected breaking changes if some relied on the persistent replacement.
• This change requires a documentation update
  • Since this is an undocumented feature, there isn't any documentation update needed for now.

How Has This Been Tested?

I have added test cases to the test suite.

Test Environment:

• OS: macOS 12.5.1
• @envelop/core: 98840fd
• NodeJS: 16.14.0

Checklist:

• I have followed the CONTRIBUTING doc and the style guidelines of this project
• I have performed a self-review of my own code
• I have commented on my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[changeset-bot]

🦋 Changeset detected

Latest commit: b27e13e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@envelop/core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@EmrysMyrddin is attempting to deploy a commit to the The Guild Team on Vercel.

A member of the Team first needs to authorize it.

[saihaj]

Thanks for the PR! while working on v3 we also fixed this issue :) cc @ardatan #1487