[BRE-372] - Clean up document start

[Eeebru]

🎟️ Tracking

• Card

📔 Objective

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.79%. Comparing base (91409a4) to head (9cd56ad). Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4915   +/-   ##
=======================================
  Coverage   41.79%   41.79%           
=======================================
  Files        1364     1364           
  Lines       64003    64003           
  Branches     5871     5871           
=======================================
  Hits        26751    26751           
  Misses      36048    36048           
  Partials     1204     1204           

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[github-actions[bot]]

Checkmarx One – Scan Summary & Details – 25240d1c-3486-404e-a176-3227fd5de048

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Passwords And Secrets - Generic Password	/test-database.yml: 181	Query to find passwords and secrets in infrastructure code.
	Passwords And Secrets - Generic Password	/test-database.yml: 104	Query to find passwords and secrets in infrastructure code.
	Passwords And Secrets - Generic Password	/test-database.yml: 188	Query to find passwords and secrets in infrastructure code.
	Passwords And Secrets - Generic Password	/test-database.yml: 68	Query to find passwords and secrets in infrastructure code.
	Passwords And Secrets - Generic Password	/test-database.yml: 91	Query to find passwords and secrets in infrastructure code.
	Passwords And Secrets - Generic Password	/test-database.yml: 110	Query to find passwords and secrets in infrastructure code.
	Passwords And Secrets - Generic Password	/test-database.yml: 79	Query to find passwords and secrets in infrastructure code.
	Passwords And Secrets - Generic Password	/test-database.yml: 184	Query to find passwords and secrets in infrastructure code.
	Unpinned Actions Full Length Commit SHA	/_move_finalization_db_scripts.yml: 102	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 514	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 206	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/_move_finalization_db_scripts.yml: 26	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 581	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/cleanup-rc-branch.yml: 20	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 547	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 630	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/_move_finalization_db_scripts.yml: 102	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/cleanup-rc-branch.yml: 20	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 547	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 581	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/_move_finalization_db_scripts.yml: 26	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 206	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 630	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build.yml: 514	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Fixed Issues

Severity	Issue	Source File / Package
	Passwords And Secrets - Generic Password	/test-database.yml: 69
	Passwords And Secrets - Generic Password	/test-database.yml: 111
	Passwords And Secrets - Generic Password	/test-database.yml: 185
	Passwords And Secrets - Generic Password	/test-database.yml: 80
	Passwords And Secrets - Generic Password	/test-database.yml: 189
	Passwords And Secrets - Generic Password	/test-database.yml: 182
	Passwords And Secrets - Generic Password	/test-database.yml: 92
	Passwords And Secrets - Generic Password	/test-database.yml: 105
	Unpinned Actions Full Length Commit SHA	/build.yml: 207
	Unpinned Actions Full Length Commit SHA	/build.yml: 631
	Unpinned Actions Full Length Commit SHA	/build.yml: 582
	Unpinned Actions Full Length Commit SHA	/_move_finalization_db_scripts.yml: 103
	Unpinned Actions Full Length Commit SHA	/cleanup-rc-branch.yml: 21
	Unpinned Actions Full Length Commit SHA	/build.yml: 548
	Unpinned Actions Full Length Commit SHA	/_move_finalization_db_scripts.yml: 27
	Unpinned Actions Full Length Commit SHA	/build.yml: 515
	Unpinned Actions Full Length Commit SHA	/build.yml: 515
	Unpinned Actions Full Length Commit SHA	/build.yml: 548
	Unpinned Actions Full Length Commit SHA	/build.yml: 631
	Unpinned Actions Full Length Commit SHA	/build.yml: 582