[Pub/sub] Add match example to API spec

[hhunter-ms]

Description

Add matches example to the pub/sub api spec

Issue reference

PR will close: #2923

[github-actions[bot]]

Stale PR, paging all reviewers

[github-actions[bot]]

Stale PR, paging all reviewers

[github-actions[bot]]

Stale PR, paging all reviewers

[msfussell]

@hhunter-ms There need to be several more changes here. Mostly the update here should follow this article https://docs.dapr.io/developing-applications/building-blocks/pubsub/howto-route-messages/ 1) See comments above on routes not route 2) In the https://docs.dapr.io/reference/api/pubsub_api/#provide-routes-for-dapr-to-deliver-topic-events section after the "In order to deliver topic events, a POST call will be made to user code with the route specified in the subscription response." sentence, say that under routes you can provide rules that match a certain condition to specific path when a message topic is received . I would also mention that you can provide a default route for any rules that do not have a specific match. 3) I would then add a link to https://docs.dapr.io/developing-applications/building-blocks/pubsub/howto-route-messages 4) Whilst we are fixing this up, can you also update

• https://docs.dapr.io/developing-applications/building-blocks/pubsub/howto-route-messages#programmatic-subscription here from saying "Node" in the tab to "Javascript" and the C# one to .NET, so this is consistent with https://docs.dapr.io/developing-applications/building-blocks/pubsub/subscription-methods/#programmatic-subscriptions
• Generally what is the name and order we have been using for languages?