fix(type): make some decorator utility functions type-safe and add some type annotations

[yetone]

Description

Some internal decorator utility functions are not type-safe now, for example:

before:

after:

I fixed the error above in this PR, but some decorators like cached_contextmanager and catch_exceptions are still not type-safe, this problem that relies on this issue: python/mypy#8645

Motivation and Context

How Has This Been Tested?

Checklist:

• My code follows the bentoml code style, both ./dev/format.sh and
  ./dev/lint.sh script have passed
  (instructions).
• My change reduces project test coverage and requires unit tests to be added
• I have added unit tests covering my code change
• My change requires a change to the documentation
• I have updated the documentation accordingly

[pep8speaks]

Hello @yetone! Thanks for opening this PR.

• In the file bentoml/_internal/utils/__init__.py:

Line 89:89: E501 line too long (142 > 88 characters)
Line 99:5: E704 multiple statements on one line (def)
Line 99:89: E501 line too long (90 > 88 characters)
Line 102:5: E704 multiple statements on one line (def)
Line 104:89: E501 line too long (139 > 88 characters)
Line 135:89: E501 line too long (103 > 88 characters)
Line 144:89: E501 line too long (102 > 88 characters)
Line 224:89: E501 line too long (134 > 88 characters)

Do see the Hitchhiker's guide to code style

[aarnphm]

This means adding mypy into our library dependency. I would rather to reserve all typeshed import under TYPE_CHECKING

[yetone]

Sorry, I forgot to add the relevant dependencies.

[aarnphm]

no worries since its only a type call i just added to the files. I think we shouldn't add mypy to library dependency anw

[yetone]

Because mypy uses typeshed types to annotate the standard libraries types during static analysis, so that mypy can only recognize the types in typeshed.

[aarnphm]

I see. I don't know if its a good practice to include mypy into library dependency. I don't see a lot of other library doing so.

[yetone]

I'm not sure how to do it, I'll research how other libraries are doing it.

[aarnphm]

LGTM

[aarnphm]

I will fix the CI related in a separate PR

[aarnphm]

We should revisit sometimes once we decide whether to go to 3.10 or 3.9 as default