CloudFormation console link resource type coverage

## 2. Scope of request
When CloudFormation provisions resources for you, you can check what it has created via the "Resources" tab on the stack.

The table lists out the Logical ID, Physical ID, Type, Status, etc.

On certain resources, the Physical ID will be a link that takes you to the page within the AWS Console that represents that resource.

One would expect that if the resource is not click-able that it doesn't exist as something viewable within the console, but this is not the case. There doesn't appear to be consistency between which resources are click-able and which ones are not.

Being able to click on the Physical ID and jump to the section of the console that describes that resource makes for quick drill-downs into what you're dealing with when looking at a stack.

## 3. Expected behavior

Any resource that can be linked to directly within the console should be linked to via CloudFormation.

Resources that don't have a presence within the console or are sub-sections of other resources should continue to behave as-is and not be linked.

## 4. Suggest specific test cases

* If you create a resource of AWS::S3::Bucket, the Physical ID column will be the name of the bucket as link to the S3 bucket within the AWS Console. 👍
* If you create a resource of AWS::ECS::Cluster, the Physical ID will be the name of the ECS Cluster, but it is not clickable even though it is possible to hotlink directly to a page for the ECS Cluster. 👎

The issue names no repository files, tests, or implementation entry points. Start by reviewing CloudFormation's Resources tab behavior for AWS::S3::Bucket and AWS::ECS::Cluster, then inventory which Physical ID values have direct AWS Console pages; done means the supported resource types link consistently while non-console resources remain unlinked.

Written by the indexing model from the issue text.