clean up UUID

[linzhp]

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature (please, look at the "Scope of the project" section in the README.md file)
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

There are still some variables and functions with "UUID" in their name, although we no longer used UUID to identify py_library targets. The gazelle_deps macro still includes the google/uuid library.

What is the new behavior?

• Change from names from "UUID" to more general "id" to hide implementation details of the id generation
• bazel run //:gazelle_update_repos to clean up google/uuid library

Does this PR introduce a breaking change?

• Yes
• No

Other information

• bazel run //:gazelle_update_repos doesn't generate the load statement correctly. I had to manually revert it back.
• We may also consider adding the py_library's module name to py_test and py_binary's deps, so it will be resolved just like regular imports and we no longer need any id for the py_library. The only problem is when a module is at the root of a Python project, the module name becomes empty, which is not valid.

[linzhp]

Don't review for now. I am exploring a different way for resolving same package imports

[linzhp]

@f0rmiga Please review #1029 first. If that PR is OK, I will reduce this PR to only clean up the deps.bzl.

[linzhp]

reduced this PR to only clean up the deps.bzl.