- MINOR: Revamped the entire check updates/autoupdates process. Going into the "Check for Updates"
        section in the main setup / configuration menu, you now have the option to subscribe to either
        the BETA or STABLE (default) track. Once you are enrolled in either of these 2 tracks, TAILMON
        will only recommend updates and autoupdates for this specific track.
      - PATCH: Fixed some minor UI changes
      - PATCH: Fixed some of the logging messaging as it was still recommending an upgrade to a stable
        release even if you were enrolled in the beta track.
      - PATCH: Made an emergency patch update because one of the cron job conditions was accidentally
        calling 'tailmon -reset', which doesn't do anything. It was supposed to run -autoupdate.

      - MINOR: Added the ability to DOWNGRADE your Tailscale version to a previous version (even a Beta
        if you so wish). This certainly is needed functionality, as the Tailscale installer does not have
        this capability built-in. This procedure was formalized, based on the step-by-step guidance from
        @Colin Taylor, @rung and @Stephen Harrington. 
      - MINOR: Implemented an email rate limiter as recently introduced in VPNMON-R3. @JGrana found that
        in a case of a network outage, that TAILMON will flood you with messages indicating that it tried
        restarting the service, only to have it loop until network connectivity is restored. This function
        creates a more formal rate limit on your emails, configured under the Configuration Menu #4, AMTM
        Email Notifications, and lets you specify how many emails you can receive per hour. An indicator
        is visible on the top right hand side of the screen, indicating "RL" (in red) as Rate Limiting
        being disabled, while "RL:10/h" (in green) showing Rate Limiting enabled, with 10 emails/hr set
        as the rate limit. 
      - PATCH: Based on a recommendation from @JGrana, the RL indicators will no longer show up on the
        main UI (or in the config display) when AMTM email functionality is turned off.
      - PATCH: Added functionality under the Main Setup & Configuration Menu that allows you to upgrade
        to the latest Tailscale (B)ETA version. Use at your own risk. You can thank @swejuggalo for this
        addition! :)
      - PATCH: Decided to remove the email notifications for when Operating Modes switch from userspace,
        to kernel, to custom. Each time the service resets, it applies the settings for these modes, and
        would shoot off an annoying email about this. 
      - PATCH: Going with recommendations from @Stephen Harrington, the ability to split out to check for
        updates between the script itself and the tailscale binaries has been completed. These options
        are set within the same "schedule autoupdate" item under the configuration menu.
      - PATCH: Expanding further on the separation of scripts/binary updates, if the TAILMON script that
        is currently running is a beta, you can now update (or autoupdate) to the next available beta.
        Thanks @swejuggalo!

      - PATCH: Modified a section of code that checks to see if the Tailscale service is dead, and tries
        to restart the service. @JGrana found that in a case of a network outage, that TAILMON will flood
        you with messages indicating that it tried restarting the service, only to have it loop until 
        network connectivity is restored. This puts a rate limiter on to only attempt this every 60
        seconds. It will also execute a fresh version of the script each time to eliminate any factors
        around that.

      - PATCH: Thanks to @jksmurf for the detailed writeup on the issues he encountered while trying to
        uninstall/reinstall TAILMON, along with issues with Entware he was dealing with. After going
        through the code, it seemed that TAILMON was bypassing the ability to use the express-install
        method if certain entware prerequisites were already installed. This has been tested and fixed!

      - PATCH: Thanks to @Wheemer1, he noticed that when hitting (R)estart, that it would overwrite the
        custom mode changes that were originally saved with the default custom mode settings. A new
        function takes care of making sure (R)estarts will now apply any custom mode changes when the
        service/connection restarts.
      - PATCH: Also, thanks to @Wheemer1 for the suggestion to formally add the '--accept-routes'
        command line argument into TAILMON. A new menu item (6) under then setup/configuration menu has
        been added that asks whether or not you want to enable this option. Special care needed to be
        taken when this option gets disabled, as a 'tailscale up --reset' command needs to be issued
        before it can be completely disabled without having to endure tailscale warnings.
      - PATCH: Thanks to @rung, added another email notification coming from TAILMON when the router
        was rebooted or manually reset, to indicate that TAILMON has restarted after an unexpected
        router reboot. TAILMON looks at router uptime, and if it's set to automatically start within
        the first 10 minutes of the router coming back up, it will send you an email.
      - PATCH: Updated some of the "site-to-site" wording changes on item #6 in the configuration/
        setup menu, and associated menu item description per @jksmurf's suggestion. Thanks!

     - PATCH: As noted by a few running older hardware and earller versions of the kernel, they were
       having trouble getting Tailscale to install correctly. This is apparently due to the fact that
       these older devices needed a different installer package. TAILMON now checks for the kernel and
       architecture, and if it matches arm7 with kernel 2.6, then it will install the tailscale_nohf
       package. Uninstall also ensures it will be removing the correctly named package. Huge thanks
       to @ColinTaylor and @jksmurf for helping distill this into a working fix within TAILMON. ;)
     - PATCH: General cleanup and organization throughout the script.

     - PATCH: Added the ability to additionally (R)estart the service/connection under the Operations
       Menu as well as the setup/configuration menu. Instead of having to s(T)op and then (S)tart the
       service, and separately stopping/starting the connection, this will do it all in one swoop. It
       may also help prevent a loss of connection while remote, as stopping anything Tailscale-related
       it typically pretty dangerous, unless you have another way back in.
     - PATCH: Added another menu item under the Setup/Configuration that will allow you to initiate a
       "tailscale up --reset" command. As of recent, with the latest changes being made to the way the
       client functions, it was necessary to issue this command in order for the connection to continue
       operating. While this command can be run manually, it was decided to incorporate this option in
       the TAILMON UI for ease-of-use. Appropriate warning language and further information has been
       added to this item (I) in the Setup/Config menu after running it.

     - PATCH: Made some wording changes based on feedback from @jksmurf in the Operation Mode screen,
       which now explicitly states that changes are made upon exit, and that if the 'Custom' mode is
       selected, that you will be able to make changes to custom settings after TAILMON completes
       making changes.
     - PATCH: Reduced the number of sleep timeouts based on feedback from @snz. This will reduce the
       amount of time you have to receive feedback on what the application is currently doing, but will
       give you the perception that its running faster now. Certain things I do not have control over:
       ie. the time it takes for Tailscale services/connection to stop and start.

     - PATCH: Increased the timer by a few seconds after the Tailscale service is started to hopefully
       reduce any possible error messages you would see when issuing a "tailscale up" command. It's a
       theory that when the service is started and not completely ready to go yet, that when the "up"
       command is given, that this may cause an benign unresponsive tailscale error message, and would
       require a successive "up" command to get it going.
     - PATCH: Included a few more Tailscale folders in the uninstall routine, as the v1.64 version of
       Tailscale adds a couple of different locations where files are being kept. These will all now be
       cleaned up after any uninstall of the Tailscale package.

     - PATCH: The Tailscale binary version is now shown in the UI on the Tailscale Service bar/header.
     - PATCH: The "Custom (O)peration Mode Settings" item in the Operations Menu is now grayed out if the
       "Custom" Operations Mode isn't selected. This item will be non-responsive unless "Custom" has been
       enabled, which will then open the Custom Operation Mode menu, allowing for full control over the
       Tailscale service switches and connection commandline switches.
     - PATCH: A new menu item in the Setup/Configuration menu will now show up if Tailscale has been found
       to be installed. The new option U(P)date will run the "tailscale update" command, and present the
       user with the choice to update to the latest available stable Tailscale version. After the update
       finishes, TAILMON will ask if you would like to reset the Tailscale service/connection (highly
       recommended), as this action will also sync previous switch settings which are wiped out when an
       update is installed.
     - PATCH: Another new menu item under the Custom Configuration menu has been added to provide TAILMON
       with a reboot protection option. Item #6 under this menu will add a command to your post-mount file
       and will launch TAILMON into its own Screen session, providing continued monitoring even after a
       router reboot occurs.