feat: CA Vacation Mode - Travel CA Policy (country-scoped temporary access)

[StoricU]

Closes #5993

[KelvinTegelaar]

start-sleep is not allowed, this will cause a massive delay in all processing and exponetionally increase costs in CIPP. a 15 second wait is already almost a $1 in wait times.

[StoricU]

Hi @KelvinTegelaar, I looked at the propagation handling in Push-ExecOnboardTenantQueue.ps1 and see the pattern of rescheduling via Add-CIPPScheduledTask with DesiredStartTime instead of using Start-Sleep.
For the Travel CA Policy, creating a Named Location and immediately referencing it in a CA policy causes error 1040 due to Graph propagation delay. Would the right approach be to split this into two scheduled tasks — one to create the Named Location, and a follow-up task (2-3 min later) to create the CA policy referencing it? Or is there a simpler pattern you'd recommend?

[KelvinTegelaar]

uses backtics, bad practice

[StoricU]

Updated based on review feedback:

• Removed all backtick line continuations — inline parameters used throughout, consistent with existing CIPP style
• Replaced Start-Sleep with a scheduled retry task for Named Location propagation (error 1040). The retry passes CountryLocationId directly to skip re-creation on subsequent attempts
• Added RetryAttempt counter with max 3 attempts to prevent infinite retry loops
• Deletion now uses IDs directly instead of searching by display name — Remove-CIPPTravelCAPolicy accepts PolicyId, Remove-CIPPTravelNamedLocation accepts LocationId
• Timezone-aware policy naming using CIPP's existing TimeSettings config with UTC fallback
• Remove-CIPPTravelCAPolicy retains fallback to display name search if PolicyId is not available