[BUG]: External location with S3A prefix create a conflict when attempting to create roles

[FastLee]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

If an external location with S3A bucket is discovered it is not matched properly for a role that is created in the create missing principals step.

Expected Behavior

No response

Steps To Reproduce

1. In sandbox create HMS tables with an S3A location reference.

Cloud

AWS

Operating System

macOS

Version

latest via Databricks CLI

Relevant log output

No response

[nfx]

use LocationTrie and this potentially should provide a better foundation

[JCZuurmond]

I do not have access to the AWS sandbox