SharePoint policy 4.2 Custom Scripting configuration options to be deprecated rego update

[ahuynhMITRE]

🐛 Summary

Microsoft is making updates to the custom scripting configuration options for Sharepoint and OneDrive. The purpose of this issue is to determine if we need to remove or revise policies MS.SHAREPOINT.4.1v1 and 4.2 based on the changes.

https://techcommunity.microsoft.com/t5/sharepoint/removing-custom-scripting-on-sharepoint-sites/m-p/4055563

As a result of #1216, two separate issues will be created to address this setting. This issue will mirror #1267's changes to setting 1.4 for consistency.

Why does this work belong in this project?

This would be useful because as Microsoft rolls out this update, users of ScubaGear will experience errors as a result of the missing setting. This allows the ScubaGear results to provide context of this change to these users preemptively.

Implementation notes

Implementation of this change shall mirror #1267

Acceptance criteria

How do we know when this work is done?

• The following files will have mirroring language and changes to match that found in Sharepoint policy 1.4 setting RequireAcceptingAccountMatchInvitedAccount seems to be deprecated or ignored #1267
  • SharepointConfig.rego
  • ReportDetails.rego
  • SharepointConfig_01_test.rego
  • sharepoint.pnp.testplan.yaml
  • sharepoint.spo.testplan.yaml