feat: update to using default scrapeclass for tls config

[zachariahmiller]

Description

add pod monitors to uds-core operator automation and UDS package CR monitor spec. update to using default scrapeClass for tls config in prometheus and "exempt" class to override default tls config update core components existing pod and service monitor implementations to fit with the new default scrapeClass implementation migrate pepr over to using the generated helm based implementation to facilitate ability to override and align zarf.yaml composition organization with the other packages. add authorization to the endpoint configuration options for monitors

Related Issue

Fixes # https://github.com/defenseunicorns/uds-core/issues/417

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Other (security config, docs update, etc)

Checklist before merging

• [ ] Test, docs, adr added or updated as needed
• [x] Contributor Guide Steps(https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md#submitting-a-pull-request) followed

[zachariahmiller]

needs docs and there are a couple of things to potentially remove that i left for someone if they wanted to test locally in review. Namely additional resources in the app-tenant test app and commented out values in the pepr chart import components values file that doesnt actually need to be there for things to work. @mjnagel If you want to take a look LMK any feedback.

After changing the behavior for the scrape classes i verified the changes i made to make the existing uds-core monitors match by deploying both from this branch and from main and doing an yaml diff of the prometheus config yaml of both deployments.

[zachariahmiller]

Made an initial attempt at the docs. Not sure how yall want to communicate new vs existing/deprecated behavior format wise especially given that these docs feed into the site.