Guard duty S3 protection doesnt honour manifest settings

[deepend-dev]

Describe the bug
S3 protection gets enabled on guard duty for all account irrespective of settings are disabled on manifest

To Reproduce

1. Disable s3protection on guardduty on manifest
   

2. It is still comes up as enabled
   

Expected behavior
S3 protection should be disabled

Please complete the following information about the solution:

• [ x ] Version: [e.g. v1.1.0]

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0021) - Video On Demand workflow with AWS Step Functions, MediaConvert, MediaPackage, S3, CloudFront and DynamoDB. Version v5.0.0". If the description does not contain the version information, you can look at the mappings section of the template:

guardduty:
    enable: true
    excludeRegions: []
    s3Protection:
      enable: false
      excludeRegions: []
    exportConfiguration:
      enable: true
      destinationType: S3
      exportFrequency: FIFTEEN_MINUTES

• Region: ap-south-1
• Was the solution modified from the version published on this repository? No
• If the answer to the previous question was yes, are the changes available on GitHub? No
• Have you checked your service quotas for the sevices this solution uses?
• Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
Add any other context about the problem here.

[crissupb]

Yes, this feature is not working as expected in the 1.1.0 release. A fix is currently in the release pipeline.

[nagmesh]

In v1.2.0 release, a fix was released for this issue.
In commit, enableS3Protection was referenced from input config and propagated to lambda function which enables the S3 protection.
Thank you for letting us know.
Have a great day!