domain_record TTLs are not rounded to closest valid values when diffing

[mgwoj]

📝 Description

ttl_sec from domain_record is accepting any integer value, but API is rounding it to nearest accepted value, causing diff on update. As a solution we also perform this rounding locally.

✔️ How to Test

ansible-test integration domain_record

[Copilot]

Pull request overview

This PR fixes idempotency issues in the linode.cloud.domain_record module when users provide a ttl_sec that the Linode API rounds to the nearest accepted TTL value, which previously caused perpetual diffs on subsequent runs.

Changes:

• Added local TTL normalization to the nearest valid TTL value during create/update of domain records.
• Expanded integration coverage to validate TTL rounding behavior (including min/max bounds) and idempotency with invalid TTL inputs.
• Updated module/docs parameter descriptions to document valid TTL values and rounding behavior.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
plugins/modules/domain_record.py	Normalizes ttl_sec to the nearest accepted TTL value before create/update to prevent spurious diffs.
tests/integration/targets/domain_record/tasks/main.yaml	Adds integration assertions for TTL rounding and idempotency when an invalid TTL is provided.
docs/modules/domain_record.md	Documents valid TTL values and clarifies that invalid values are rounded to the nearest valid TTL.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.