feat: Make resolveValue protected

[gurgunday]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

Hey! It would be useful if resolveValue was protected instead of private, that way it can be used in Guards that extend ThrottlerGuard. Especially when canActivate is modified, we still need to process ThrottlerOptions, so having access to super.resolveValue would prevent repetitive code

What is the new behavior?

resolveValue is callable from child classes

Does this PR introduce a breaking change?

• Yes
• No

Other information

[micalevisk]

I guess resolveValue is more like an internal utility, which is why it is not public. And, to make sense of this, you may have to code the whole logic of retrieving those routeOrClass* variables as well.

Instead of changing this (an leaking internals stuff), we could have high-level methods to extract those parameters somehow, I guess?

throttler/src/throttler.guard.ts

Lines 119 to 128 in ec79d77

	const limit = await this.resolveValue(context, routeOrClassLimit || namedThrottler.limit);
	const ttl = await this.resolveValue(context, routeOrClassTtl || namedThrottler.ttl);
	const blockDuration = await this.resolveValue(
	context,
	routeOrClassBlockDuration || namedThrottler.blockDuration || ttl,
	);
	const getTracker =
	routeOrClassGetTracker || namedThrottler.getTracker || this.commonOptions.getTracker;
	const generateKey =
	routeOrClassGetKeyGenerator || namedThrottler.generateKey || this.commonOptions.generateKey;