Block some amp-ad RTC callouts using amp-geo

### Description

Hi! As a publisher, we use a handful of amp-ad RTC callouts from different providers to optimize our header bidding. One of these providers supports TCFv2, the other provider does not. In the EEA, we'd like to be able to send RTC requests to Provider 1, but never to Provider 2 (regardless of consent). However, `block-rtc` only supports blocking *all* or *none* of the RTC callouts from a slot, and `sendRegardlessOfConsentState` only supports *adding* to the consent states during which a RTC callout will be sent, not *removing* the default `SUFFICIENT` consent state.

### Alternatives Considered

We initially implemented this using `block-rtc`, but that means that we'd have to stop using Provider 1 in the EEA, just because of Provider 2's lack of support. At the current time, this is the compromise we'll have to go with to ship Provider 2, which is detrimental to our revenue.

### Additional Context

Let me know if you have any other questions!

Start by tracing amp-ad RTC callouts and reading the existing block-rtc and sendRegardlessOfConsentState behavior. Define how amp-geo should distinguish individual providers and verify the EEA case: Provider 1 remains callable while Provider 2 is never called, including regardless of consent.

Written by the indexing model from the issue text.