feat(standards): add TAP lifetime and length configuration

[jspern]

add TAP lifetime and length configuration

Expose minimum, maximum, and default TAP lifetime along with TAP length as configurable options on the Enable Temporary Access Passes standard.

Previously only the single-use/multi-logon toggle was exposed, and the lifetime and length values silently fell back to the Set-CIPPAuthenticationPolicy parameter defaults.

Validate the configuration before contacting Graph: the run is skipped with an error when the minimum lifetime exceeds the maximum, or when the default lifetime falls outside that range, rather than issuing a PATCH that Graph would reject. Absolute bounds are surfaced in the form via field validators.

Drift detection, remediation, and the standards comparison report now cover all five settings.

[KelvinTegelaar]

wondering two things, haven't audited full code path yet:

1.) Is it backwards compatible and will it not alert on drift for people that have not modified their standard

2.) should we introduce this, or recommend the complete auth settings standard instead?

[jspern]

@KelvinTegelaar

1. I believe since the existing TAP standard is just falling back to the Microsoft defaults there shouldn't be any conflict for drift, and it should be backwards compatible as well for anyone currently using it
2. My understanding is that the problem with the complete auth policy standard is it's not possible to implement a granular change to only one of the policies without affecting all the others unless you are already using the complete standard. So for example, if someone was just using the standalone TAP standard to enable TAP with the default settings, and they were not using the complete auth policy standard, if they wanted to then use the complete standard to make a change ONLY to the TAP policy for all their managed tenants, they would be forced to overwrite the settings for all of the other policies as well, which is a problem when different tenants have policies configured differently. The ideal final goal I think would be to split out each of the auth policies into their own standards, and eliminate the complete one altogether, or leave it available as a legacy standard.