Leverage NR's change tracking endpoint to resolve deprecation warnings on deployments

[fallwith]

With https://github.com/newrelic/newrelic-ruby-agent/pull/1461 we updated the agent to dynamically choose between 2 different API endpoints to signal that an application deployment had taken place.

But now as discussed in #2240, using the agent for signaling deployments will result in a deprecation warning that recommends switching to "our all-new NerdGraph API" as explained in the change tracking docs.

The use of one fully supported New Relic tool should not result in deprecation warnings thrown by another. The Ruby agent ought to be updated to make use of the new change tracking endpoint when presented with customer keys that are compatible with it.

[workato-integration[bot]]

https://new-relic.atlassian.net/browse/NR-179040