Support for dynamic DCR names with creating CCP based Data Connectors

[dragosinc-sentinel]

Is your feature request related to a problem? Please describe.
We are looking to update our Dragos CCP to support connections to multiple API endpoints. We have previously talked with @danielzatakovi about how something similar is done in the Okta Single Sign-On Connector and have a working solution.

The downside of this approach is that the multiple data connectors all use a single Data Collection Rule (DCR). This makes it difficult to track metrics associated with a single data connector as they all report metrics to a single DCR, with no way to distinguish them.

Describe the solution you'd like
We'd like to have a way better track metrics with multiple Data Connectors from a single CCP. A few possible solutions are:

• Allow us to create multiple DCRs so that there is a one-to-one mapping between a data connector instance and a DCR
• Keep the single DCR, but add some extra dimension to the metrics so we can separate out the metrics by data connector.

Describe alternatives you've considered
You can achieve something similar by manually creating DCRs and data connectors via the Rest API. While useful for development and debugging this approach isn't viable for our customers.

Additional context
N/A