Implement multiple filters on consumers

[bruth]

Overview

See #192. Validation occurs on the server, this would be scoped to allowing a consumer to set SubjectFilters as an array/list/slice on the ConsumerConfig.

The behavior is documented in ADR-34.

Clients and Tools

• [x] Schemas @ripienaar https://github.com/nats-io/jsm.go/pull/441
• [x] CLI @ripienaar https://github.com/nats-io/natscli/pull/728
• [ ] Terraform @ripienaar
• [x] Github Actions @ripienaar
• [x] Go @piotrpio
• [x] Java @scottf https://github.com/nats-io/nats.java/pull/965
• [x] JavaScript @aricart https://github.com/nats-io/nats.deno/pull/469
• [x] .Net @scottf https://github.com/nats-io/nats.net/pull/821
• [ ] C @levb
• [x] Python @wallyqs
• [ ] Ruby @wallyqs
• [x] Rust @Jarema @caspervonb

Other Tasks

• [x] docs.nats.io updated @bruth
• [ ] Update ADR to Implemented
• [ ] Update client features spreadsheet

Client authors please update with your progress. If you open issues in your own repositories as a result of this request, please link them to this one by pasting the issue URL in a comment or main issue description.

[bruth]

@ripienaar For the schema and CLI, it appears you checked these off, but the PRs apply to the metadata fields rather than support for multiple subject filters.

[ripienaar]

@ripienaar For the schema and CLI, it appears you checked these off, but the PRs apply to the metadata fields rather than support for multiple subject filters.

thanks, fixed!