Feature Request: Allow duplicate IMS org ID in Launch configuration

We have a use case where we want to send the event to two different Edge configurations, based on whether or not the user consented to cookies. Currently it seems as there is no way to do this.

**Allow duplicate IMS org ID across Alloy instances**
The 2 edge configurations we have are under the same IMS org ID - but they're simply configured differently (different AA report suites etc)

**Hot-switch / change configuration in the "Send Event" action**
To avoid having 2 rules of every single tracking type, it would be great if you could in the "Send Event" action somehow target what configuration ID you are targeting, possibly through a Data Element.

```
return hasConsent ? alloy : alloyCookieless;
```

Start by reviewing how IMS org IDs are validated in Launch configuration and how the Send Event action selects an Edge configuration. Done means two Alloy instances can use the same IMS org ID and Send Event can target the consent-dependent configuration described in the issue.

Written by the indexing model from the issue text.