Declare __all__ in public subpackages

[r4victor]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Add __all__ to kubernetes.config, kubernetes.stream, kubernetes.utils, kubernetes.watch and their kubernetes.aio counterparts so that type checkers treat their documented functions and classes as public, which they stopped doing once the package shipped py.typed.

Which issue(s) this PR fixes:

Fixes #2724

Special notes for your reviewer

• Why __all__ rather than as aliases: kubernetes.informer and kubernetes.aio already declare their exports with __all__, and it leaves the existing imports untouched.
• Why no tests: CI doesn't run a type checker, and that's the only place the failure shows up.
  • A runtime check that every imported name is in __all__ would wrongly fail when a name is imported for internal use only.
  • A hardcoded list of names would just duplicate __all__.
  • A type checker in CI would be the real guard, but that's a bigger change than this fix.

Does this PR introduce a user-facing change?

Fixed type checkers such as pyright reporting documented functions and classes in `kubernetes.config`, `kubernetes.stream`, `kubernetes.utils`, `kubernetes.watch` and their `kubernetes.aio` counterparts, for example `config.load_kube_config` and `utils.create_from_yaml`, as not exported since v37.0.0. Wildcard imports such as `from kubernetes.config import *` no longer import unrelated names like `exists` and `expanduser`.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: r4victor / name: Victor Skvortsov (520673c)

[kubernetes-prow]

Welcome @r4victor!

It looks like this is your first PR to kubernetes-client/python 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/python has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[yliaog]

/lgtm
/approve

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: r4victor, yliaog

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [yliaog]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment