[service] [request]: Add Default Toleration For Guardduty Addon

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Please add default toleration for Amazon Guardduty agent add-on as it is for other add-ons so it will deploy on all nodes regardless of their taints:

```
tolerations:
- operator: Exists
```

**Which service(s) is this request for?**
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I want the guardduty agent to be able to be deployed into every node group so the whole cluster can be monitored regardless of taints applied.

**Are you currently working around this issue?**
We are aware we can manually patch the daemonset via a kubernetes manifest, but would prefer a solution that is AWS/EKS sided as per the output of describe-addon-configuration for the addon.

**Additional context**
N/A

**Attachments**
N/A

Start by reviewing the EKS add-on configuration and the Amazon GuardDuty agent deployment behavior described in the issue. Confirm how the existing Kubernetes tolerations are represented for other add-ons and whether the requested default is supported; done means the GuardDuty agent can deploy on nodes with taints without manual DaemonSet patching.

Written by the indexing model from the issue text.