Create oic storage account in dev

[cadenmarchese]

Which issue this PR addresses:

https://issues.redhat.com/browse/ARO-5029

What this PR does / why we need it:

• Creates storage account in dev environments, named after the resource group so that we have unique names
• Uses template function to remove dashes from storage account names - our resource groups commonly have dashes (v4-eastus, aro-australiaeast, aro-shared-cluster, etc...) and the storage account names don't allow these.
  • Also ensures storage account name doesn't exceed 24 characters.
• Creates role assignment on the RP MSI in a full env, or the RP service principal in a shared env
• Updates docs
• Keeps deployment of oic resources separate from other ARM templates to maintain reusability

Uses AKS and AZWI storage account examples as inspiration.

Test plan for issue:

• Tested applying this template: https://portal.azure.com/#view/HubsExtension/DeploymentDetailsBlade/~/overview/id/%2Fsubscriptions%2Ffe16a035-e540-4ab7-80d9-373fa9a3d6ae%2FresourceGroups%2Foictest%2Fproviders%2FMicrosoft.Resources%2Fdeployments%2Frp-oic
• Tested a full RP service in dev to confirm that the role assignment is attached to the right MSI: https://portal.azure.com/#@redhat0.onmicrosoft.com/resource/subscriptions/fe16a035-e540-4ab7-80d9-373fa9a3d6ae/resourceGroups/marches-aro-eastus/providers/Microsoft.ManagedIdentity/userAssignedIdentities/aro-rp-eastus/azure_resources

Once the PR is approved and merged I can go and apply this to our shared environments.

Is there any documentation that needs to be updated for this PR?

Yes - updated.

[hlipsig]

LGTM

[SudoBrendan]

If anonymous/unauthenticated access to this SA is a requirement, LGTM - I'm not sure if we need that or not?