style: release whole repository

Today, developers must take care to include sources in the `filegroup(name = "standard_package")` targets which are sprinkled around the repository.
In the best case, omitting one will be caught by automated testing in the repo. However,
- it's a lot of effort to add sufficient test coverage for this
- we still won't catch everything.

I also claim there is no benefit to having Bazel build the release artifact. `git archive` is completely sufficient for this task (including pruning directories that are unnecessary in the release artifact and which make it large)

Making this change would simplify the repository so that it's more feasible for us to maintain it with a very small effort.

Start by locating the `filegroup(name = "standard_package")` targets mentioned in the repository and reviewing how Bazel currently builds the release artifact. Compare that flow with `git archive`, including the stated directory pruning needs. Done means the release artifact no longer depends on manually maintained source lists and retains the required contents without Bazel building it.

Written by the indexing model from the issue text.