Fix service name generation to enforce RFC 6763 length limit

[garethsb]

Truncate mDNS service instance names exceeding 63 bytes with a hash suffix to ensure RFC 6763 compliance, since Avahi does not automatically truncate like mDNSResponder. Also use underscore rather than colon as the host/port separator, and declare service_name in the header. Add unit tests for service_name.

Made-with: Cursor

[garethsb]

@lo-simon, @jonathan-r-thorpe, looks like the AMWA test suite is taking 40+ minutes to run, is that expected?

[lo-simon]

Some minor suggestions.

[garethsb]

@lo-simon any idea why two of the Windows 2022 runners failed fast?

[lo-simon]

@lo-simon any idea why two of the Windows 2022 runners failed fast?

I have seen that before; most of the time, when I re-run the runner, the problem disappears.

According to Google, in a CI/CD environment, the runner might have multiple network interfaces active.

When Get-NetIPConfiguration runs:

1. It expects to find one primary configuration to output.
2. If it finds multiple configurations, it returns an array (System.Object[]).
3. Internally, the command attempts to map these results to a property (likely NetAdapter) that is strictly defined to hold only one instance at a time.

To fix that, as we just need any valid IP config to proceed, pipe it to Select-Object -First 1 as shown below:

Get-NetIPConfiguration | Select-Object -First 1

[garethsb]

To fix that, as we just need any valid IP config to proceed, pipe it to Select-Object -First 1 as shown below:

Get-NetIPConfiguration | Select-Object -First 1

Hey, @lo-simon, we probably want to put the Select-Object -First 1 after the Where-Object?

[lo-simon]

To fix that, as we just need any valid IP config to proceed, pipe it to Select-Object -First 1 as shown below:
Get-NetIPConfiguration | Select-Object -First 1

Hey, @lo-simon, we probably want to put the Select-Object -First 1 after the Where-Object?

Nice, @garethsb, let's open another PR for this fix.