Update the FIPS ingest limitations for Oracle #9245

Blocked by: elastic/integrations#22330

deploy-manage/security/fips-ingest.md is maintained by hand. It currently says both of these:

• Under Metricbeat limitations: "The Oracle module is not supported."
• Under "Elastic Integrations that are not FIPS compatible": a link to the Oracle integration.

After the Beats and integrations changes, those two statements are wrong. The generic SQL entries stay correct, because FIPS builds still reject every SQL driver except Oracle.

Scope

• Remove the Oracle integration from the unsupported-integrations list.
• Replace the Oracle module bullet with a short caveat: supported only when the customer installs an Oracle client whose provider is FIPS 140-3 validated, with a link to the integration FIPS section.
• Leave these in place: the SQL module bullet, and the SQL, MySQL, PostgreSQL, and MSSQL integrations.

Done when

• The page no longer lists the Oracle integration as unsupported.
• The Oracle module caveat matches the integration README.
• The SQL module and the other database integrations are still listed as not supported.