refactor: Bazelrc presets: Almost always use common

[hofbi]

Best practice seems to be to almost always use common(reminding me to C++'s AAA rule). Using common ensures that build, fetch, and query use the same flags and is easier for users since there is one recommended way to do it.

With bazelbuild/bazel#18609, Bazel does not fail in case a flag does not belong to a common, so there is no harm in using common for Bazel 6.3+. Because of this, bazel6.bazelrc does not use common.

I kept all test flags as is for now, but we can also make them common if we want, either here or as follow up PR.

[hofbi]

@fmeum What are your thoughts on doing the same for test, e.g. all test becomes common in the bazelrc presets? Do you see any issues/potential harm in doing this? E.g., would setting

bazel-lib/.aspect/bazelrc/correctness.bazelrc

Line 64 in f048405

test --experimental_fetch_all_coverage_outputs

to common cause coverage output downloads also for bazel build calls?

[fmeum]

I am not aware of any downside and there is even a minor upside: Before Bazel 9, --test_env invalidates build commands and thus shouldn't be set on test.

[hofbi]

I am not aware of any downside and there is even a minor upside: Before Bazel 9, --test_env invalidates build commands and thus shouldn't be set on test.

#1099 does it