Legacy Code: Connection to monitor port 49100 failed!

Describe the bug

This is not a bug that appears to be impacting functionality. But just a note about legacy code leaving trails in the logs. Confirmed this is legacy with a member of the team.

[2023-04-26 07:57:59Z ERR JobNotification] Connection to monitor port 49100 failed!
[2023-04-26 07:57:59Z ERR JobNotification] System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (111): Connection refused [::ffff:127.0.0.1]:49100

To Reproduce
N/A

Expected behavior
Legacy code to be removed.

Runner Version and Platform

[2023-04-26 07:57:58Z INFO Listener] Runner is built for Linux (X64) - linux-x64.
[2023-04-26 07:57:58Z INFO Listener] RuntimeInformation: Linux 5.15.0-1035-azure #42-Ubuntu SMP Tue Feb 28 19:41:23 UTC 2023.
[2023-04-26 07:57:58Z INFO Listener] Version: 2.303.0
[2023-04-26 07:57:58Z INFO Listener] Commit: e676c7871817c1b484299cd93fabdf4b95e70741

OS of the machine running the runner?

Linux 5.15.0-1035-azure #42-Ubuntu

What's not working?

N/A

Job Log Output

N/A

Runner and Worker's Diagnostic Logs

N/A

Start by searching the runner source for the JobNotification message and monitor port 49100, then trace the legacy connection path that produces the log. Done means the obsolete code is removed and the connection-refused messages no longer appear, without changing runner functionality.