AWS Lambda support for PrincipalOrgID in resource-based policies

### Name of the resource

AWS::Lambda::Permission

### Resource Name

_No response_

### Issue Description

This [blog post](https://aws.amazon.com/about-aws/whats-new/2022/03/aws-lambda-principalorgid-resource-policies/) says that PrincipalOrgID support has been added to CloudFormation, but the documentation doesn't mention it and adding a `PrincipalOrgID` property fails.

### Expected Behavior

`PrincipalOrgID` property should add a `aws:PrincipalOrgID` condition to the policy

### Observed Behavior

> Encountered unsupported property PrincipalOrgId

### Test Cases

```yaml
Type: AWS::Lambda::Permission
Properties:
Action: lambda:InvokeFunction
FunctionName: MyFunction
Principal: "*"
PrincipalOrgID: o-12346asdf
```

### Other Details

_No response_

Start by reviewing the linked AWS Lambda announcement and the AWS::Lambda::Permission YAML example in the issue. Confirm whether PrincipalOrgID is accepted and produces an aws:PrincipalOrgID condition in the resulting resource-based policy; the issue does not name repository files or tests.

Written by the indexing model from the issue text.