flag_alias and custom flags do not appear in explicit_cmd_line field of OptionsParsed BES message

[alex-torok]

Description of the bug:

When using a --flag_alias or a custom flag on the command line, they do not appear on the explicit_cmd_line field of the OptionsParsed BES message.

Even though these are custom flags, I would expect them to appear in the explicit_cmd_line field of OptionsParsed, since the naming of the field suggests that it is exactly the flags passed to the bazel command.

Which category does this issue belong to?

CLI

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

A sample repo that reproduces the issue can be seen here.

Which operating system are you running Bazel on?

linux

What is the output of bazel info release?

release 7.2.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

I haven't seen any issue discuss explicit_cmd_line or the OptionsParsed message

Any other information, logs, or outputs that you want to share?

No response