[CI] Add support to test packages with basic subscription

[mrodm]

Proposed commit message

Update CI scripts and tools (ReportFailedTests) to allow run Elastic stack with other subscriptions.
Currently, it is just supported "basic" and "trial".

Added new mage targets to get the subscription set in the package:

 $ mage -l 
Targets:
  check                       
  clean                       
  importBeats                 
  isSubscriptionCompatible    checks whether or not the package in the current directory allows to run with the given subscription (ELASTIC_SUBSCRIPTION env var).
  mergeCoverage               
  modTidy                     
  reportFailedTests     

Author's Checklist

• Test packages with "basic" subscription. https://buildkite.com/elastic/integrations/builds/24439
• Ensure that packages with "enterprise" or "platinum" subscriptions are filtered out if "basic" is set. https://buildkite.com/elastic/integrations/builds/24439
• Test in Dry-Run mode creation of scripts. https://buildkite.com/elastic/integrations/builds/24442#01961133-5dd3-4a73-a55c-add3433af641
• Remove changes for debugging in go.mod, go.sum and .buildkite/scripts/common.sh.

How to test this PR locally

# test some package
cd packages/<package>
elastic-package stack up -v -d -U stack.elastic_subscription=basic
elastic-package test -v
elastic-package stack down -v

# test creation of scripts
DRY_RUN=true CI_MAX_TESTS_REPORTED=1 BUILDKITE_BUILD_URL=https://buildkite.com/elastic/integrations/builds/20643 SERVERLESS=false STACK_VERSION=9.0.0-SNAPSHOT ELASTIC_SUBSCRIPTION=basic VERBOSE_MODE_ENABLED=true  mage -v ReportFailedTests build/test-results

Related issues

• Relates Allow to run Elastic stack with other licenses elastic-package#2501

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[mrodm]

This value could be changed in the follow-up PR to include LogsDB too.

[mrodm]

It would return failure if there is any failure (e.g. failed to read YAML file), and success in any other case (zero value).
When it returns success, the message echoed will show whether or not it is compatible (true or false).

[mrodm]

For both cases, this function will return failure (code 1). Depending on the message echoed, the caller method should take one or other action.

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 383240f

Failed CI Steps

• Check integrations apache_spark

History

• 💔 Build #24568 failed d32eb44
• 💔 Build #24567 failed 4eea916
• 💚 Build #24559 succeeded 7560c46
• 💔 Build #24549 failed fcfc90a
• 💔 Build #24540 failed 4b5a98d

cc @mrodm

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube