BED-5070: Add Auto-provisioning Support to SSO Auth Flow on Backend

[ALCooper12]

Description

• Created a new SSOProviderConfig struct to be used as a jsonb type/value inside the sso_providers table under a new column called config
• Added database migration in order to create the new config column and insert default values
• Updated and added new/existing database and model variables/functions within sso_providers.go,samlprovider(s).go, and oidc_providers.go files
• Added user creation auto-provisioning and attribute mapping for both SAML and OIDC
• Set up the enforcement of enable/disable auto-provisioning for the SSOProviderConfig

Motivation and Context

• Ticket: BED-5070

Why is this change required? What problem does it solve?

• Currently, BloodHound users must be created manually for every new user. In larger customer environments, this can create a significant amount of work to create 30+ user accounts and this friction could reduce adoption. This PR solves the issue of auto-provisioning users who don't yet exist via SAML and OIDC into the BHCE/BHE platform. It also sets up default user role allocation and SSO Provider role modification

How Has This Been Tested?

• Still working on this*****

Screenshots (optional):

• Still working on this*****

Types of changes

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Database Migrations

Checklist:

• I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Issues and Pull Requests README #672
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up-to-date
  • Open API docs
  • Code comments (GoDocs / JSDocs)
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed