chip-device-ctrl: do not hardcode UDP listen port

[bluebin14]

Problem

chip-device-ctrl hardcodes the UDP listen port to CHIP_PORT+1. This makes it impossible to have more than one instance of the python controller on the same host. The target device is unable to tell which one is which and messages arrive to both which results in communication failure.

Change overview

Do not hardcode the UDP listen port.

Testing

How was this tested? (at least one bullet point required)

• tested manually, running 2 simultaneous instances of python controller, performing full commissioning with each (PASE + CASE) followed by read/write commands to make sure everything works. This was not possible to do before this change.

Notes

A similar fix can be applied to chip-tool but that hasn't been tested yet so it is not included here.

[github-actions]

Size increase report for "esp32-example-build" from 51c9327

File	Section	File	VM
chip-temperature-measurement-app.elf	.flash.text	-60	-60

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-persistent-storage.elf and ./pull_artifact/chip-persistent-storage.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-all-clusters-app.elf and ./pull_artifact/chip-all-clusters-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-pigweed-app.elf and ./pull_artifact/chip-pigweed-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-shell.elf and ./pull_artifact/chip-shell.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-lock-app.elf and ./pull_artifact/chip-lock-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-ipv6only-app.elf and ./pull_artifact/chip-ipv6only-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-temperature-measurement-app.elf and ./pull_artifact/chip-temperature-measurement-app.elf:

sections,vmsize,filesize
[Unmapped],0,60
.flash.text,-60,-60

Comparing ./master_artifact/chip-bridge-app.elf and ./pull_artifact/chip-bridge-app.elf:

sections,vmsize,filesize

[jmeg-sfy]

What happens with a zero as parameter then, it s dynamically choose a port to listen to..?

[bluebin14]

Yes, zero means use any (dynamic) port. This is a standard Unix convention.

[bzbarsky-apple]

This is OK as far as it goes, but only because we never end up resolving the controller's mdns advertisement so far. If we did, it would break, because the mdns advertisement always advertises CHIP_PORT.

Of course that was broken before this change too....