feat: add alias sshfp naptr and ptr records

[zachsmith1]

This pull request adds support for three new DNS record types—ALIAS, SSHFP, and NAPTR—across the API, CRDs, controller logic, and integration tests. It also introduces a PowerDNS Recursor sidecar to enable ALIAS record resolution and updates the PowerDNS configuration accordingly. The changes ensure that these new record types are fully supported end-to-end, including validation, deep copy methods, CRD schemas, and integration with the PowerDNS backend.

New DNS Record Types Support:

• Added support for ALIAS, SSHFP, and NAPTR record types in the API type definitions, including new struct definitions (ALIASRecordSpec, SSHFPRecordSpec, NAPTRRecordSpec) and updates to the RRType enum and RecordEntry struct.

CRD and Validation Updates:

• Extended the DNSRecordSet and DNSZoneDiscovery CRDs to include ALIAS, SSHFP, and NAPTR types, along with their schemas and validation rules.

Controller Logic Enhancements:

• Updated the PowerDNS client logic to handle the new record types, including proper formatting and normalization of ALIAS, SSHFP, and NAPTR records when building RRsets.

PowerDNS and Sidecar Configuration:

• Added a PowerDNS Recursor sidecar container to the deployment to enable authoritative expansion of ALIAS records, and updated the PowerDNS configuration to use the local recursor for ALIAS resolution.

Testing:

• Extended end-to-end integration tests to cover the new ALIAS record type, ensuring correct behavior.

[drewr]

@brian-toresdahl-datum Where does this fit in your story arc around HTTPS/SVCB?

[drewr]

@zachsmith1 What functionality does this unlock that helps users?

[zachsmith1]

@drewr ALIAS/ANAME records are on @brian-toresdahl-datum roadmap and the others are the next most commonly used record types so that we are closer to what providers like cloudflare, google dns, etc offer