Support for disabling policy enforcement for policy sets assignments

[SenthuranSivananthan]

Overview/Summary

Based on guidance from CAF - Adopting policy driven guardrails, we should allow for policy set assignments to have enforcement mode turned on (enabled/default) or off (disabled/DoNotEnforce).

This flexibility will allow departments to adopt policy guardrails with limited change in their environment through Policies until they are ready for automation.

Implementation adds a new enforcementMode parameter to each policy set assignment deployment. This parameter's default value is Default which translates to enabled. The possible values for this parameter are Default (means Enabled) or DoNotEnforce (means Disabled).

This change should be configurable per policy set assignment and affects built-in and custom policy sets.

This PR fixes/adds/changes/removes

Fixes #119

Breaking Changes

None

Testing Evidence

When enforcementMode = Default - Passed

When enfocementMode = DoNotEnforce - Passed

Custom Policy - Tags - the policy has Deny rules and policy set assignment enforcementMode = DoNotEnforce. Expect that the resource groups (RGs) can be created without the required tags. The policy will mark the RG as non-compliant, but will not block the creation of RGs.

1. Tag policy assignment configuration

2. RG created without any tags
   

3. Policy marks RG as non-compliant

As part of this Pull Request I have

• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Updated relevant and associated documentation.

[hudua]

Edits look good! Verified that all built-in policy assignments and custom assignments had enforcement mode as configurable.