Adjust tests to run with security enabled

[jkakavas]

As part of #72300 we are explicitly disabling security for certain tests, not because this is strictly required but because these tests were written with the assumption that security is disabled ( trial or basic license without explicit configuration ). We ( as in the elasticsearch team with guidance and help from the es-security team ) should take up the effort and adjust these tests so that they can run with our default configuration which is that security is enabled.

• Various enrich tests:
  • BasicEnrichTests
  • EnrichMultiNodeIT
  • EnrichPolicyUpdateTests
  • EnrichPolicyChangeIT
  • EnrichProcessorIT
  • EnrichProcessorMaxMatchesIT
  • EnrichResiliencyTests
  • EnrichRestartIT
  • EnrichSourceDataChangeIT
• TransformInternalIndexIT
• TransformNoRemoteClusterClientNodeIT
• TransformNoTransformNodeIT
• CCSTermsEnumIT
• qa/os/src/test/java/org/elasticsearch/packaging/util/Archives
• qa/os/src/test/java/org/elasticsearch/packaging/util/Packages
• Packaging Tests

[elasticmachine]

Pinging @elastic/es-security (Team:Security)

[joegallo]

I'm adding a new enrich test in #133752 that also doesn't have security, so I've added it to the above list, and I totally intend (next week) to look into making all these enrich tests run with security enabled.