Move Metricbeat azure module to GA and add final tests

[narph]

What does this PR do?

• Replaces the beta label with ga
• Adds tests for checks that all fields are documented, these should be replaced with an implementation for Add test checking that all fields are documented  #17315

Why is it important?

Move the azure module to GA

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Closes Move metricbeat azure module to GA #16024

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[exekias]

This is looking good, but it's not testing the fields that come out of the different metricsets

I think it's ok for the lightweight metricsets as you only need to test that in monitor, but the rest need some more checks

[narph]

@exekias , regarding:

I think it's ok for the lightweight metricsets as you only need to test that in monitor, but the rest need some more checks

The field mapping for the other native metricsets looks like this (ex.):

- name: compute_vm.*.*
  release: beta
  type: object
  object_type: float
  object_type_mapping_type: "*"
  description: >
    compute_vm

No other fields but the ones the dynamic mapping covers.
We also cannot predict that all the metricnames will be mapped in one event since we are making separate calls to the azure rest api depending on the timegrain, supported aggregation, namespace etc. and events will have different metrics based on those filters.

[exekias]

We agreed on keep adding tests here: #17315