chore(ci): enable continuous fuzzing

[heitorlessa]

Issue number: #2203

Summary

Enables continuous fuzzing for every PR file change and every 6th hour against the entire code base.

To prevent a negative experience in PR reviews until fuzzing completes, this PR limits to 90 seconds. For safety, we use continuous batching async which run for a longer period (1 hour) to increase our chances to find bugs -- e.g., memory leaks, dangling pointers from C-extensions, buffer & integer overflows, etc.

Addresses OSSF Scorecard recommendation

Changes

Please provide a summary of what's being changed

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[heitorlessa]

Closing due to reduced bandwidth. Will try after re:Invent or next year