[MAJOR/BREAKING] Adding OIDC login functionality

[MariusStorhaug]

Description

Closing #1450

POCing the OpenID Connect passwordless logon mechanism for Azure AD.

Pipeline references

Pipeline

https://github.com/MariusStorhaug/ResourceModules/runs/6661434629?check_suite_focus=true#step:4:235

Type of Change

Please delete options that are not relevant.

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• My corresponding pipelines / checks run clean and green without any errors or warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (readme)
• I did format my code

[jontreynes]

Curious, is the ARM_CLIENT_ID just a string of the app registration id guid?

[MariusStorhaug]

@mblant Any input from you regarding swapping out the current SPN + Secret with OIDC federation for GH Action logon? It another breaking change but think we should lead by example and push customers to a more secure setup. Thoughts?

[MariusStorhaug]

@jontreynes ARM_CLIENT_ID is indeed the GUID appID of the app registration yes.