AML Compute Instance fails to build - Invalid Name format

Describe the bug
When adding an AML Compute Instance User Resource to a workspace, the deployment will fail if:

1. the AML workspace name ends in four numeric characters and
2. the Compute Instance Resource Id ends in four numeric characters

If the above two conditions apply, this results in an 'InvalidResourceName' error, with the following error message: "A name for an Azure ML Compute Instance must be between 3 and 24 characters in length and must use only numbers, letters and minus symbol (-) and must start with letters. Numbers cannot be the ending of the name if the previous character is a minus symbol (-). Please specify a different Azure ML Instance name"

Steps to reproduce

1. Deploy an AML Workspace Service with a resource id ending in four numbers (e.g. 794d166a-d426-4050-be63-e0de1e174098)
2. Deploy an AML Compute Instance with a resource id ending in four numbers (e.g. 440c0bae-c370-4b64-a8e5-0000ab006653)
3. Deployment fails with 'InvalidResourceName' error (ci-40986653)

Source of Error

The error derives from the code in templates/workspace_services/azureml/user_resources/aml_compute/terraform/locals.tf:

  aml_compute_id                 = "${local.short_service_id}${local.short_user_resource_id}"
  aml_compute_instance_name      = "ci-${local.aml_compute_id}"

Start in templates/workspace_services/azureml/user_resources/aml_compute/terraform/locals.tf and reproduce the deployment using workspace and compute instance resource IDs ending in four digits. Trace how aml_compute_id and aml_compute_instance_name produce ci-40986653, then verify the deployment succeeds with valid Azure ML naming for those inputs.