Solace-AMQP: document configurable address prefixes and other AMQP 1.0 brokers

[nelson-parente]

Thank you for helping make the Dapr documentation better!

Please follow this checklist before submitting:

• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• Read the contribution guide
• Commands include options for Linux, MacOS, and Windows within tabpane
• New file and folder names are globally unique
• Page references use shortcodes instead of markdown or URL links
• Images use HTML style and have alternative text
• Places where multiple code/command options are given have tabpane

In addition, please fill out the following to help reviewers understand this pull request:

Description

Documents the two new metadata fields of the Solace-AMQP pub/sub component, topicAddressPrefix and queueAddressPrefix, added in dapr/components-contrib#4539.

The component prepends topic:// or queue:// to the AMQP address of every destination, which is how Solace distinguishes a topic from a queue. Those two prefixes are now metadata fields, so the same component can be used with other AMQP 1.0 brokers that address destinations differently. This adds:

• the topicAddressPrefix and queueAddressPrefix rows to the spec metadata table
• a table in Publishing/subscribing to topics and queues showing how a topic name becomes an AMQP address
• moves Create a Solace broker above the new section so the broker-specific content is not nested under the metadata reference
• a Using other AMQP 1.0 brokers section covering both ways to line the addresses up with the broker (Artemis acceptor prefixes, or addressing by name from Dapr) with an Apache ActiveMQ Artemis component example

Issue reference

dapr/dapr#10363

Implementation PR: dapr/components-contrib#4539