FilterChainMatch: Add metadata match criteria

[tonya11en]

Add connection metadata match criteria for filter chain matching.

I have a use-case involving tagging various tenant connections' dynamic metadata with some ID in a listener filter. I'd like to use that metadata as filter chain matching criteria. As far as I can tell, there's currently no way to influence filter chain matching via the dynamic metadata for a connection.

I see that #18685 is opened for custom matcher extensions, but in my opinion that is overkill for what I'm trying to do and others would benefit from this change.

If this sounds like a reasonable ask, I (or someone in my group) can submit a patch.

[mattklein123]

There is #18685 and also #3411.

I realize that we can quickly add this, but it's just going to make the existing problem worse. Are there any resources for reworking how this configuration is handled via both extensions as well as configurable ordering?

[tonya11en]

@mattklein123 let me talk with some folks and see if I can get some resources allocated to do this the right way.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.