feat: support new consent resolution strategy values

[saikumarrs]

Description

Besides, "and" and "or" consent resolution strategies, we're now supporting the new "all" and "any" values. The UI changes will be rolled out very soon.

Also, the logic now prefers to use "allowed consent IDs" and falls back to "denied consent IDs" to align with the client side implementation. It's a bit tricky with allowed consent IDs as some older SDK versions send it as an object for OneTrust CMP.
So, we're handling both an object and array of strings.

Additionally, I've sanitized the consent IDs from the config and event before resolving them for filtering events to destinations.

Linear Ticket

https://linear.app/rudderstack/view/scrum-board-75b83c60706a5

Security

• The code changed/added as part of this pull request won't create any security issues with how the software is being used.

[Copilot]

Pull Request Overview

This PR adds support for the new consent resolution strategy values ("all" and "any") alongside the existing "and" and "or". It also updates the processing logic to prioritize "allowed consent IDs", fall back to "denied consent IDs", and sanitize consent IDs before filtering events.

• Changed the type of AllowedConsentIDs from interface{} to []string.
• Modified the filtering logic in getConsentFilteredDestinations to accommodate new resolution strategies.
• Enhanced consent ID processing and sanitation in getConsentManagementInfo.

[codecov]

Codecov Report

Attention: Patch coverage is 95.31250% with 3 lines in your changes missing coverage. Please review.

Project coverage is 76.94%. Comparing base (01a7b83) to head (5390400).
Report is 5 commits behind head on master.

Files with missing lines	Patch %	Lines
processor/consent.go	95.31%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5798      +/-   ##
==========================================
- Coverage   76.98%   76.94%   -0.05%     
==========================================
  Files         491      491              
  Lines       67415    67469      +54     
==========================================
+ Hits        51900    51914      +14     
- Misses      12694    12724      +30     
- Partials     2821     2831      +10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull Request Overview

This PR implements support for new consent resolution strategies ("all" and "any") and adjusts logic to prefer allowed consent IDs while handling legacy OneTrust CMP formats. Key changes include:

• Updated test expectations for destination filtering in processor_test.go.
• Refactored consent management parsing in consent.go to support both object and array formats for allowed consent IDs.
• Added sanitation of consent IDs before filtering events.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
processor/processor_test.go	Updated test expectations to match changes in the consent resolution logic.
processor/consent.go	Enhanced parsing and sanitation logic for consent IDs, supporting new and legacy formats.

Comments suppressed due to low confidence (1)

processor/consent.go:74

• [nitpick] Adding inline comments within each case of the resolution strategy switch (for 'any'/'or' and 'all'/'and') could help clarify the intended logic differences and ease future changes.

switch finalResolutionStrategy {

[Copilot]

Pull Request Overview

This PR adds support for new consent resolution strategy values ("all" and "any") and adjusts the consent filtering logic accordingly. Key changes include updated test expectations in processor_test.go and enhancements to consent handling in processor/consent.go to support both array and object formats for allowed consent IDs.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
processor/processor_test.go	Updated expected destination counts in tests to match new logic
processor/consent.go	Revised consent processing for allowed and denied consent IDs, including legacy support for OneTrust CMP

Comments suppressed due to low confidence (1)

processor/processor_test.go:3656

• The updated test expectation reflects the new consent resolution logic. Please verify that these new expected values accurately capture the intended filtering behavior across all relevant cases.

).To(Equal(6)) // all except D6, D13, and D14

[Copilot]

Pull Request Overview

This PR introduces support for new consent resolution strategy values ("all" and "any") and adjusts the logic to prefer allowed consent IDs while handling both object and array formats for legacy OneTrust CMP data. Key changes include updated test expectation values for consent filtering, enhancements in parsing and sanitizing consent IDs, and revised resolution strategy logic.

• Update tests to reflect new resolution logic
• Enhance getConsentManagementInfo to support multiple types for AllowedConsentIDs and sanitize inputs
• Adjust consent filtering logic in getConsentFilteredDestinations per new strategies

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
processor/processor_test.go	Updated expected count values in tests to reflect the new consent filtering logic
processor/consent.go	Revised consent parsing and sanitization, and added support for new resolution strategies

Comments suppressed due to low confidence (1)

processor/processor_test.go:3656

• Verify that the updated expected count values in the tests accurately reflect the new consent filtering logic and confirm that the comments remain consistent with the actual behavior.

).To(Equal(6)) // all except D6, D13, and D14