Refine remote.it operations, now that connectd systemd service is gone, and considering 3 valid states for /etc/remoteit/registration

[holta]

remote.it Device Packages 4.15.2 removed their connectd "parent" systemd service as of 2022-09-07. So instead of bouncing their connectd service, going forward, we'll instead run /usr/share/remoteit/refresh.sh which should generally do the exact same thing.

This PR aims for a cleaner all-around solution to remote.it frailties.

Recognizing that /etc/remoteit/config.json may or may not exist a priori (with or without a claim code) and that /etc/remoteif/registration can be in any one of 3 states {doesn't exist, is empty to block registration handshake, OR contains a [presumably valid!] remoteit_license_key} ...until remote.it is enabled by either...

• sudo /usr/bin/iiab-remoteit

Or...

• ./runrole remoteit which runs roles/remoteit/tasks/enable-or-disable.yml (after you set remoteit_enabled: True in /etc/iiab/local_vars.yml)

Needs testing in coming days!

Building on:

• PR New command /usr/bin/iiab-remoteit to quickly obtain a new Claim Code for https://remote.it (allows remote connections to manage an IIAB) #3161
• PR remoteit/tasks/enable-or-disable.yml: Don't fail if svc(s) missing #3363

[holta]

Tested quite thoroughly on 64-bit RasPiOS Lite on RPi 4.

Thanks if others can test this on other OS's and other hardware in coming days and weeks!