Resolve potential IDs conflicts between Kibana dashboards

[mtojek]

As there is chance of naming (ID) conflict between Kibana dashboards, it's advised to prepend a package name.

There are few action items identified that can help in resolving the issue:

• Prepare some script to prepend the package name to the dashboard id. Ideally we should do the same with the existing dashboard links: Prefix dashboard IDs with package names #319 @ycombinator
• Release new package revisions for 7.10+ @ycombinator
• Add some validations to elastic-package for future packages: Validate that Kibana asset IDs start with lowercase package names package-spec#65 @mtojek
• Add this logic to the migration script. Fix import-beats: prepend module names to Kibana dashboards #322 @mtojek (in review)

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[mtojek]

Promotion from snapshot to staging:
elastic/package-storage#497
elastic/package-storage#498

[mtojek]

Promotion from staging to production
elastic/package-storage#499
elastic/package-storage#500

[mtojek]

Branches merged, let's wait for Jenkins jobs to finish, packages will be deployed tomorrow.

[mtojek]

Affected packages have been promoted.

[botelastic]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!