release-24.3: dev: remove --strip=never configuration from .bazelrc.user

[blathers-crl]

Backport 1/1 commits from #137804 on behalf of @rickystewart.

/cc @cockroachdb/release

---

Previously we unconditionally disabled stripping; however, this has a negative impact on performance (linking gets much more expensive when you do not strip). This is a cost we paid both locally in the development cycle as well as in CI.

Removing this line from .bazelrc restores the default behavior of stripping iff the compilation_mode is fastbuild (which is the default). This will give developers the desired quick iteration behavior. You now have to opt into disabling stripping.

Going forward we may evaluate if it is worth it to disable stripping for unit tests in CI to enable the use of side-eye (#136839). Until that point, there is no reason to disable stripping in this context.

Stripping can be enabled with --strip=always or by passing -c dbg or -c opt. Notably, dev build --cross, the release process, and the roachtest nightlies all currently use -c opt when building, so there is nothing else to be done in these cases: they are all correctly not stripping.

Epic: CRDB-17171
Release note: None

---

Release justification: Non-production code changes

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Backports should only be created for serious
  issues or test-only changes.
• Backports should not break backwards-compatibility.
• Backports should change as little code as possible.
• Backports should not change on-disk formats or node communication protocols.
• Backports should not add new functionality (except as defined
  here).
• Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
• All backports must be reviewed by the owning areas TL. For more information as to how that review should be conducted, please consult the backport
  policy.

If your backport adds new functionality, please ensure that the following additional criteria are satisfied:

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
• Your backport must be accompanied by a post to the appropriate Slack
  channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

[cockroach-teamcity]

This change is