access_log(grpc): pass command parsers to custom tags (fix DNS filter validation)

[garimauttam]

Fixes #43396

What this PR does

When DNS filter access logs use gRPC logger custom_tags with formatter-style values, validation can fail because extension command parsers are not propagated into gRPC custom tag creation.

This PR threads command_parsers through the gRPC access log path so custom tag formatter values can resolve extension-specific commands (including DNS filter commands).

Changes

• Plumb command_parsers from gRPC access log config factories (http_config/tcp_config) into gRPC access log impls.
• Update CommonPropertiesConfig to accept command parsers.
• Pass command parsers to Tracing::CustomTagUtility::createCustomTag(...).
• Add a regression test in tcp_config_test to verify custom tag formatter values respect injected command parsers.

Why this fixes the issue

The failure came from building formatter-based custom tags without the extension parser set. After this change, custom tag parsing uses the same parser chain provided by the access log call site, so DNS-specific formatter commands are recognized correctly.

Testing

• bazel test //test/extensions/access_loggers/grpc:tcp_config_test //test/extensions/access_loggers/grpc:http_config_test

Risk

Low. The change is scoped to parser propagation for gRPC custom tag construction and includes targeted regression coverage.

[repokitteh-read-only]

Hi @garimauttam, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #43457 was opened by garimauttam.

see: more, trace.

[AntonKanug]

@yanavlasov i had #42915 already open with the same changes + the requested integration tests and was waiting on review FYI