AWS::CloudFormation::Macro , ModuleVersion, ResourceVersion, and defaults should be shareable through RAM

## Scope of request

CloudFormation allows us to define Macros, Resources, and Modules within a single account-region. We would like to make the objects we define in a given region available to all accounts within our organization. Right now this requires instantiating a StackSet that targets an OU.

AWS provides RAM Resource Shares as a means of sharing objects across accounts. We should be able to publish CloudFormation Macros, Resources, and Modules in a RAM share for use in our various accounts, then use them from CloudFormation in a separate account as though they had been defined natively.

## Expected behavior

```yaml
---
Parameters:
ModuleUrl:
Type: String
MacroLambda:
Type: String
OU:
Type: String
Resources:
Macro:
Type: AWS::CloudFormation::Macro
Properties:
Name: MyMacro
FunctionName: !Ref MacroLambda
Mod:
Type: AWS::CloudFormation::ModuleVersion
Properties:
ModuleName: This::Is::My::MODULE
ModulePackage: !Ref ModuleUrl
ModDefault:
Type: AWS::CloudFormation:ModuleDefaultVersion
Properties:
Arn: !Ref Mod
Share:
Type: AWS::RAM::ResourceShare
Properties:
Name: MyShare
Principals:
- !Ref OU
ResourceArns:
- !Ref Macro
- !Ref Mod
- !Ref ModDefault
```

## Category

Management

No repository files, tests, or entry points are named. Start by reviewing the resource types in the example—AWS::CloudFormation::Macro, ModuleVersion, ModuleDefaultVersion, and AWS::RAM::ResourceShare—and the requested cross-account behavior. Done means these CloudFormation objects can be published through a RAM share and consumed from other accounts as described.

Written by the indexing model from the issue text.