feat: Add support for hierarchical ARNs in Arn utility

[murphm8]

Reason for this change

Some AWS services are beginning to provide hierarchical arns for finer grained resource permissions management. AWS PCS is one of those services.

Description of changes

The Arn utility has been updated to support properly resolving the resource and resourceName for hierarchical ARNs. Previously, using the slash ARN support, it would return the parent resource type for resource and resourceName would include the entire rest of the ARN string.

I attempted to make this as minimal a change as possible. I followed TS best practices adding an optional "options" argument to the Split method in order to support hierarchical ARN depth configuration.

Describe any new or updated permissions being added

None

Description of how you validated changes

Added unit tests for the hierarchical ARN support, and existing unit tests continue to pass.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ Features must contain a change to a README file.
❌ Features must contain a change to an integration test file and the resulting snapshot.
❌ The first word of the pull request title should not be capitalized. If the title starts with a CDK construct, it should be in backticks "``".

If you believe this pull request should receive an exemption, please comment and provide a justification. A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed, add Clarification Request to a comment.

[murphm8]

I think there are gaps here for arns like

Fixed prefix and multi-slash resourceType values: https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsiotgreengrass.html#awsiotgreengrass-resources-for-iam-policies

Fixed Prefix: arn:${Partition}:aws-marketplace::${Account}:${Catalog}/ReportingData/${FactTable}/Dashboard/${DashboardName} where ${Catalog} is a prefix. - https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsmarketplacesellerreporting.html#awsmarketplacesellerreporting-resources-for-iam-policies

Another gap in coverage would be for https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsorganizations.html#awsorganizations-resources-for-iam-policies

Other possibilities: https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonlookoutforequipment.html#amazonlookoutforequipment-resources-for-iam-policies

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: f736efa
• Result: FAILED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[aws-cdk-automation]

This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. Note that PRs with failing linting check or builds are not reviewed, please ensure your build is passing

To prevent automatic closure:

• Resume work on the PR
• OR request an exemption by adding a comment containing 'Exemption Request' with justification e.x "Exemption Request: "
• OR request clarification by adding a comment containing 'Clarification Request' with a question e.x "Clarification Request: "

This PR will automatically close in 14 days if no action is taken.

[aws-cdk-automation]

This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.