feat: PRSDM-9506 frontmatter spike

[FabioSol]

Description

this pr contains the default configuration for the configurable frontmatter. This configuration should follow the schema defined in the frontmatter-config-design/, Additionally it was determined that the module frontmatter configutation file should have this:

the module/frontmatter-config.yml

the final complete configuration will be calculated running hugo like this:

hugo --config config.yml, frontmatter-config.yml

and it will be used to generate a schema for frontmatter validation.

Issue

• 📋 JIRA_TICKET_URL

Screenshots

PR Readiness Checks

• Your PR title conforms to conventional commits <type>: <jira-ticket-num><title>, for example: fix: PRSDM-123 issue with login with a maximum of 100 characters
• You have performed a self-review of your changes via the GitHub UI
• Comments were added to new code that can not explain itself (see reference 1 and reference 2)
• New code adheres to the following quality standards:
  • Function Length (see reference)
  • Meaningful Names (see reference)
  • DRY (see reference)
  • YAGNI (see reference)

[DustinFischer]

@FabioSol
How have you tested this PR? I'm concerned how this will actually work.
It's still unclear to me what your proposed merge stratgey is for the frontmatter epic.
Is your proposed merge strategy documented anywhere?
I don't mean how Hugo merges configs, I mean how we plan to merge frontmatter configs for Presidium (which will probably rely on Hugo's merge features)