Add clearer testing and cost to run of reference architectures

What does this MR do and why?

Add cost to run and test details of all 7 reference archs to documentation into 2 tables

Review app link: http://main-ee-78705.178.62.207.141.nip.io/ee/administration/reference_architectures/index.html

Tasks:

• Add table for Testing section - Validation and test results
• Link test results for all sections
• Add table for cost to run.
• Link calculated cost to all GCP sections.
• Change links in all RA docs to point to Cost to run table
• Create issue for next iteration:
  • Update Cost to run table for 10k in all environ... (gitlab-org/quality/reference-architectures#105 - closed)
  • Build 50K environment on AWS - Cloud Native (gitlab-org/quality/reference-architectures#106 - closed)
  • Build a test environment on Azure - Omnibus (gitlab-org/quality/reference-architectures#107 - moved)
  • Explore regular performance test of a 10k AWS S... (gitlab-org/quality/reference-architectures#112 - closed)
  • Move 1k and 2k to Weekly instead of Daily (gitlab-org/quality/reference-architectures#109 - closed)
  • Add Test coverage for all reference architectures (gitlab-org/quality/reference-architectures#110 - closed)
  • Review Cost to run section in our Reference arc... (gitlab-org/quality/reference-architectures#111 - closed)

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.