Basic Refactoring: Type Annotations, Final & Const Usage

[Marc-R2]

This PR introduces some basic refactoring to improve code readability and maintainability:

• Added type annotations where possible for better static typing
• Replaced variables with final where applicable to ensure immutability
• Used const for constant values (optimize performance)

These changes don't affect the functionality of the package but should improve the overall code quality.

I will continue to break down the larger changes into smaller PRs for easier review and integration.

Thanks!

[lamnhan066]

Hi @Marc-R2

Please let me know if a package or your opinion suggests those changes?

I'm on the way to find a package that has better suggestions than regular lints so we have better code even when adding new code.

Thank you for your PR.

[Marc-R2]

@lamnhan066

These changes are based on some lint-rules from the very_good_analysis 6.0.0 (rules) package.

I like this package, but sometimes some of the rules are a bit harsh. I usually disable (or ignore) at least avoid_print, comment_references and no_duplicate_case_values.
In my experience, code with these lints is very consistent, easy to read, and prevents many problems at compile-time.

I would be happy to add more of these lints if you want.

[lamnhan066]

Thank you.

I’ll merge your code and add the very_good_analysis as a dependency after reviewed and all the tests are passed. Sometimes the compiled Worker will have unexpected behaviors when we use a static type instead of a dynamic one.

[lamnhan066]

We should wrap this code with unawaited instead of using await here because we already used queue.completer.future in return.

[lamnhan066]

LGTM!

Thank you for your contributions.