Description of problem:
After satellite-change-hostname has been completed successfully, at the end, the same command asks to re-register the client using old deprecated method.

Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch


How reproducible: Always


Steps to Reproduce:
1. Run below command on Satellite machine to change its hostname.

       # satellite-change-hostname new_sat_fqdn --username admin --password redhat

2. Allow the command to execute successfully.


Actual results: The command throws below output on screen at the end.

~~~~~~~~~~
**** Hostname change complete! ****
IMPORTANT:

  You will have to install the new bootstrap rpm and reregister all clients and Capsules with subscription-manager
  (update organization and environment arguments appropriately):

  yum remove -y katello-ca-consumer*
  rpm -Uvh http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm
  subscription-manager register --org="Default_Organization" --environment="Library" --force

  Then reattach subscriptions to the client(s) and run:

  subscription-manager refresh
  yum repolist


  On all Capsules, you will need to re-run the satellite-installer with this command:

  satellite-installer --foreman-proxy-foreman-base-url https://satellite.example.com \
                                  --foreman-proxy-trusted-hosts satellite.example.com

  If Puppet is enabled on the Capsule, add the following to the installer command:

                                  --puppet-server-foreman-url https://satellite.example.com

  Short hostnames have not been updated, please update those manually.
~~~~~~~~~~

Here we are asking user to manually remove the katello-ca-consumer package, install the new katello-ca-consumer package and then re-run 'subscription-manager register' command which is a deprecated method now.


Expected results: Instead of above method, we should ask user to generate curl command using Global Registration Template method and use it to re-register the client machine back with Satellite.


Additional info: "Chapter 3. Registering Hosts to Satellite" in following documentation: https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/managing_hosts/index?lb_target=preview&check_logged_in=1