Support service listeners with multiple addresses

[gabordozsa]

Fixes issue issues #1813 and #1814

Add support for multi-routing-key listeners.

• Extend tcpListener entity witth a multiAddressStrategy field
• Add new entity type ListenerAddress to the management scheme
• Add configure and delete management APIs to the ListenerAddress entity
• Modify adaptor_listener and tcp_listener C files to use a service address list

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[ted-ross]

Using the following config, the router crashes on shutdown.

router {
    mode: interior
    id: A
}

listener {
    host: 0.0.0.0
    port: amqp
}

tcpListener {
    name: choices
    port: 8080
    multiAddressStrategy: none
    address: choice-1
}

There is an assertion failure:

src/adaptors/adaptor_listener.c:126: _listener_free: Assertion 'DEQ_IS_EMPTY(li->addresses)' failed.

[gabordozsa]

Using the following config, the router crashes on shutdown.

router {
    mode: interior
    id: A
}

listener {
    host: 0.0.0.0
    port: amqp
}

tcpListener {
    name: choices
    port: 8080
    multiAddressStrategy: none
    address: choice-1
}

There is an assertion failure:

src/adaptors/adaptor_listener.c:126: _listener_free: Assertion 'DEQ_IS_EMPTY(li->addresses)' failed.

I think it is fixed now.

[gabordozsa]

The PR is ready for review now. I have run some basic tests it in my local development environment to create and delete ListenerAddresses with different priorities. New connections have picked a reachable service address with highest priority - as expected.

Follow up work items for the multi-address listeners:

• Extend status information to include a list of reachable addresses
• VANFLOW records
• New system test for the priority failover strategy