chore: add better logging around NATS connections

[connorsmith256]

Feature or Problem

This PR:

• adds the host ID, actor ID, and link name to the name of each NATS connection. This should increase the ability of operators to debug whether NATS connections related to the provider are still alive
• adds with_connection_event_logging to NATS clients, which logs on connection events (which should be rare, including once on initial connection)
• adds an error log if the stream for any subscriber closes unexpectedly

Related Issues

Release Information

v0.17.4

Consumer Impact

N/A

Testing

Built on platform(s)

• x86_64-linux
• aarch64-linux
• x86_64-darwin
• aarch64-darwin
• x86_64-windows

Tested on platform(s)

• x86_64-linux
• aarch64-linux
• x86_64-darwin
• aarch64-darwin
• x86_64-windows

Unit Test(s)

Acceptance or Integration

Manual Verification

Tested manually in a lattice. Deleted and recreated links on the provider to test that NATS connections were dropped from the server:

nats server report connections -j | jq '.[] | .name' | rg Messaging | wc -l

[brooksmtownsend]

This will be super nice to know when the provider has unexpected issues