Enabling SSL Broker for Remote Agents breaks Elastic Agent connectivity

Summary

When enabling SSL connectivity for remote agents by changing the Broker URL and Broker Client URL protocols from tcp:// to ssl://, elastic agents are no longer able to connect

Steps to Reproduce

1. Start an Elastic Agent and run a test build to confirm Elastic Agents are connecting
2. Stop the Elastic Agent
3. Change the Broker URL and Broker Client URL, replacing "tcp://" with "ssl://" as per Securing your remote agents.
4. Start the Elastic Agent again

Expected Results

Elastic agent connectivity should continue working after enabling SSL for remote agents

Actual Results

Elastic Agents never successfully connect to Bamboo but instead sit in "Pending" forever

Workaround

Securing your remote agents cannot be used in conjunction with Elastic Agents