Expand param files in the execution log with --expand_param_files (#31808)
### Description
`--expand_param_files` now also applies to the arguments recorded by `--execution_log_{compact,binary,json}_file`. Spawns are still executed with param files and the execution log still records the param files as inputs, so input digests are unaffected.
### Motivation
This makes it possible to analyze full command lines from the execution log, e.g. to estimate the effect of path mapping across configurations.
### Build API Changes
No
### Checklist
- [x] I have added tests for the new use cases (if any).
- [ ] I have updated the documentation (if applicable).
### Release Notes
RELNOTES: `--expand_param_files` now also expands the arguments persisted in the execution log.
Closes #31808
COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31808 from fmeum:execution-log-expand-param-files d1bd91cae5ff7eb54c451f5a274b35befaaf3208
PiperOrigin-RevId: 1009134630
Change-Id: I3c577693fa2c554171f71ed22e63f9a3b4e16603
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
