feat: Add schedule scaling possibility

[mfroembgen]

Description

Additionally, it would be nice to use schedule scaling for ddb tables. (https://docs.aws.amazon.com/autoscaling/application/userguide/get-started-exercise.html)
If you want to save cost with PROVISIONED but have for example an import job that needs a lot of capacity it's the only option to not run into scaling issues.

Motivation and Context

If you want to save cost with PROVISIONED but have for example an import job that needs a lot of capacity it's the only option to not run into scaling issues.

Breaking Changes

No, as it is only an additional option.

Draft

This is just a draft of how It could be implemented. I'm open to superior solutions as I know its kinda bad practice.

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[mfroembgen]

@antonbabenko Do you maybe have time to share your opinions on that, please?

[mfroembgen]

@antonbabenko Can you maybe have another look at it, please? Please let me know what you think 🙂

[mfroembgen]

@antonbabenko Just a friendly reminder that I'm still looking for another review :)

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[github-actions]

This PR was automatically closed because of stale in 10 days

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.