[FIPS] Collect user facing documentation notes

[simitt]

Add your comments for user facing documentation notes for

• Elastic Agent
• Fleet Server
• Beats

[kaanyalti]

The following introduce x/crypto dependencies into the agent and cannot easily be removed

github.com/elastic/beats/v7/metricbeat/module/mongodb
github.com/elastic/beats/v7/metricbeat/module/kvm/dommemstat
github.com/elastic/beats/v7/x-pack/filebeat/input/gcppubsub
github.com/elastic/beats/v7/libbeat/processors/translate_ldap_attribute (will be removed) @kruskall
github.com/elastic/beats/v7/libbeat/processors/add_cloud_metadata
github.com/elastic/beats/v7/x-pack/filebeat/input/azureeventhub

We need to let our users know that they need to deploy their agent/beats in a fips environment if they were to use service providers like gcp/azure/mongo in order to be compliant.

More detailed discussion on this issue can be found here https://github.com/elastic/ingest-dev/issues/5039

[shmsr]

Hi. I am part of @elastic/obs-infraobs-integrations team. We would like to share a few more module names that should not be used in order to maintain compliance.

• x-pack/metricbeat/module/sql
• x-pack/metricbeat/module/oracle
• metricbeat/module/postgresql
• metricbeat/module/mysql
• metricbeat/module/mongodb

Reason for including these names is mentioned in this comment: https://github.com/elastic/obs-integration-team/issues/151#issuecomment-2744447477

We do not have to disable it, right? I read some comments and it seems we do not need to disable them.

[simitt]

Removed functionality is listed in https://docs.google.com/document/d/1lsLvq_-Q1a9Wa5lkhEr_TRW4X1RQ-rcvuiW4_3gHCvg/edit?pli=1&tab=t.0#heading=h.mwkjf62lj11b.