[TT-14041] feat: do not track API key

[antonipy]

Description

Related Issue

#6857

Motivation and Context

As we have some keys that don't need analytics, we would like to have the option to not track specific keys.
We have keys that are either used for monitoring or some high load keys that can overwhelm our analytics database or ramp up the costs of our log aggregator.

How This Has Been Tested

I've created 2 keys:

• 1 with DoNotTrack enabled
• 1 with DoNotTrack disabled

The enabled key is not being tracked, while the disabled one is tracked.
Rate limiting and the quota work for both keys.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactoring or add test (improvements in base code or adds test coverage to functionality)

Checklist

• I ensured that the documentation is up to date - feat: add do_not_track parameter tyk-docs#5950
• I explained why this PR updates go.mod in detail with reasoning why it's required
• I would like a code coverage CI quality gate exception and have explained why

[andyo-tyk]

Hi @antonipy,

Thanks for this contribution. We've had this in mind for some time (just without it rising to the top of the priority list) so will definitely do a detailed review of your proposal. Please bear with me, as we need to consider potential side-effects on other components in the solution.

Thanks again for the great idea.

[antonipy]

Hi @antonipy,

Thanks for this contribution. We've had this in mind for some time (just without it rising to the top of the priority list) so will definitely do a detailed review of your proposal. Please bear with me, as we need to consider potential side-effects on other components in the solution.

Thanks again for the great idea.

Hi @andyo-tyk, let me know if I can help with anything. :)