Generate a namespace prefix for managed tags

[kpollich]

With the introduction #165655, duplicate tag names are prevented by Kibana. This means Fleet technically has an edge case where if a user creates a Managed tag or a tag with a name that matches an integration's title property before installing an integration, Fleet will fail to create the tag due to the collision.

One way we could fix this is by prefixing our "fleet sourced" flags with something like Elastic: to guarantee (or at least more convincingly guarantee) that we won't see collisions related to our tags.

cc @drewdaemon

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[drewdaemon]

Supporting work on Kibana tagging (for example, preventing users from creating tags with the chosen prefix) can be requested from @elastic/appex-sharedux if it makes sense.

[sebelga]

I like the suggestion that those managed resources (and the Elastic:) prefix are own by either core or SharedUX team. Making sure those are created at bootstrap time internally.

[jen-huang]

I'm going to transfer this to SharedUX team. This is low priority from Fleet team's perspective since it is an edge case.

[drewdaemon]

@jen-huang if your team isn't interested in tracking this problem, I don't think we need to keep this issue open.

Fleet is the one creating the tags, so Fleet would be the team to make the changes adding the Elastic: prefix. I only mentioned Shared UX team in case you went the route of the prefix and wanted the tag system to stop customers from using the same prefix when they create their own tags, in which case that team could help.