[DNS DATA] Update name_in_zone to set default as None for Python Client

[rsingh4infoblox]

Summary

Sets name_in_zone to default to None on the Record model so that records without a name prefix (e.g. apex records) can be created without supplying this field. Also adds compartment_id support for DNS Zone scoping, as noted in the PR description.

Type of Change

• 🆕 New API / Model
• 🔧 Update Existing Schema or Model
• 🐛 Bug Fix
• 📝 Documentation
• 🧹 Maintenance (dependency upgrades, CI, refactoring)

Affected Packages

• anycast
• cloud_discovery
• dfp
• dns_config
• dns_data
• dtc
• fw
• infra_mgmt
• infra_provision
• ipam
• ipam_federation
• keys
• redirect
• upgrade_policy
• universal_ddi_client

Resource / Model: Record
Description: Made name_in_zone optional with a default of None; added compartment_id field for Zone scoping.

Schema Changes

• New model added
• New field(s) added to existing model
• Field(s) removed or renamed
• Required fields changed

Detailed Changes (click to expand)

File	Change
src/dns_data/models/record.py	Changed name_in_zone to Optional[str] = None; added compartment_id field
src/dns_data/docs/Record.md	Updated field documentation to reflect optionality and new field

Ticket / Issue

Fixes #28 and #29

Changelog Inclusion

• Consider for changelog and release notes addition

Additional Context

Previously, omitting name_in_zone would cause a validation error even for apex-level records where no name prefix is expected. Setting the default to None allows the field to be omitted and lets the API apply its own default behaviour.