connect: Add support for ConsulResolver to specifies a filter expression

[pierluc-codes]

Description

Add Filter to ConsulResolver to be able to specifies an expression for filtering the query results.

PR Checklist

• updated test coverage
• external facing docs updated
• not a security concern

I don't know how secure is hashicorp/go-bexpr

[vercel]

@pierluc-codes is attempting to deploy a commit to the HashiCorp Team on Vercel.

A member of the Team first needs to authorize it.

[banks]

This LGTM, Thanks for contributing!

I have one minor optional suggestion inline but fine to merge as is!

[banks]

nit: we view tags as a semi-deprecated construct in Consul registrations - everything that can be done with tag can also be done with Meta and Filter. Long term we'd like to consolidate on just Meta but have never been able to prioritize the one or two places (e.g. DNS) where tags still do something that Meta doesn't currently.

So I'd accept this - it's not wrong and we've not officially announced or documented that "tags" are deprecated, but it is for example the reason we don't support tag filters in connect endpoints etc.

Would you be open to writing this test using Meta instead? It's not a huge deal either way, but internally we'd tend towards supporting/encouraging use of meta of tags as we might one day get around to deprecating and removing tags entirely!

[curtbushko]

Thanks for doing this!