Databricks Workspace missing identity output

**Bicep version**
azd version 1.0.2

**Describe the bug**
When creating a Databricks Workspace an User-Assigned Managed Identity is created out of the box.
It does not appear to be any way to create this ID separately and supply refer to that resource, and the Databricks Workspace creation output does not contain this ID.

Ref. https://learn.microsoft.com/en-us/azure/templates/microsoft.databricks/workspaces?pivots=deployment-language-bicep

As such it seems impossible to use the bicep role assignment to provide the required permissions to the Databricks cluster (i.e. to an Azure Storage Account) using the Microsoft.Authorization/roleAssignments resource provider.

**To Reproduce**
Steps to reproduce the behavior:

Deploy a Databricks Workspace:
```bicep
param name string
param location string = resourceGroup().location
param tags object = {}

@description('Specifies whether to deploy Azure Databricks workspace with Secure Cluster Connectivity (No Public IP) enabled or not')
param disablePublicIp bool = false

@description('The pricing tier of workspace.')
param sku object = {
name: 'trial'
}
param managedResourceGroupName string = ''

resource databricks 'Microsoft.Databricks/workspaces@2018-04-01' = {
name: name
location: location
sku: sku
tags: tags
properties: {
managedResourceGroupId: managedResourceGroup.id
parameters: {
enableNoPublicIp: {
value: disablePublicIp
}
}
}
}

resource managedResourceGroup 'Microsoft.Resources/resourceGroups@2021-04-01' existing = {
scope: subscription()
name: managedResourceGroupName
}
```

**Additional context**
Add any other context about the problem here.

Potential solutions:
1. (Preferred) Output details of the automatically created User-Assigned Managed Identity in the Dataspace Workspace resource output.
2. (Preferred) Support "bring-your-own" identity (i.e. I can create a user-assigned managed identity in the bicep before supplying it to the Databricks Workspace resource creation).
3. Being able to delay/sequence an existing resource (i.e. dependsOn support), so that I can lookup the auto-generated identity as an existing resource AFTER it is automatically created.