Add "Force" flag to the Destination Policy property in a AWS::Logs::Destination resource

### Name of the resource

AWS::Logs::Destination

### Resource name

_No response_

### Description

A **"Force" flag** is requested for the "DestinationPolicy" property in **AWS::Logs::Destination** resource.
Currently CloudFormation does not support the update of existing Destinations using a policy that specifies an OrgID principal, such in this example :
{
"Version" : "2012-10-17",
"Statement" : [
{
"Sid" : "",
"Effect" : "Allow",
"Principal" : {
"AWS": "*"
},
"Action" : "logs:PutSubscriptionFilter",
"Resource" : "arn:aws:logs:region:999999999999:destination:testDestination",
"Condition": {
"StringEquals" : {
"aws:PrincipalOrgID" : ["o-1234567890"]
}
}
}
]
}

Currently, the use of this policy in a cloudformation stack is only possible when creating a new Destination and it is not possible for updating existing Destinations that used to accept (*) or account ID as a principal instead of OrgID principal.

Customers currently are not able to update their stacks because of this matter, instead, they have to use CLI :
aws logs put-destination-policy
\ --destination-name "testDestination"
\ --access-policy file://~/AccessPolicy.json
\ --force

Please consider adding this flag.

### Other Details

_No response_

No repository files, tests, or entry points are named. Start by reviewing the AWS::Logs::Destination request and the shown aws logs put-destination-policy command, including its --force option. Done means stack updates can apply a DestinationPolicy using an OrgID principal to an existing destination.

Written by the indexing model from the issue text.