bk: use latest FIPS VM images and stop using catalog-info step but GH actions validation

[v1v]

What is the problem this PR solves?

• Use the latest VM image for FIPS - that's how it works with the rest of the images.
• Stop using the catalog-info step in BK - github-action: add catalog-validate for GitHub actions #4890 supported this in GH actions.

How does this PR solve the problem?

Run faster rather than always and delegate the responsibility to the existing tooling.
Align the same VM image strategy regardless of FIPS or non-fips.

How to test this PR locally

Design Checklist

• I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
• I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
• I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

• 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/fragments using the changelog tool

Related issues

[prodsecmachine]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[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