Improvements for Updating to 1.4.0 WebGUI Version

[Martinski4GitHub]

• Various code improvements and fine-tuning for updating to the latest 1.4.0 WebGUI version.
  The goal is to allow for a "smooth transition" from the previous 1.3.10 to the new 1.4.0 version with WebGUI support.

The latest changes allow users to update to 1.4.0 using the 1.3.10 CLI menu option to update the script or via a direct SSH command:

/jffs/scripts/MerlinAU.sh forceupdate

There's no longer a need to have a special "extra argument" as I had originally proposed. This makes it easier for users to update without remembering to add an extra parameter.

• Fixed error with "Toggle F/W Build Type" menu option
  A "buildtypechoice: parameter not set" error was found when using the CLI menu option to "Toggle F/W Build Type" and the user presses only the <ENTER> key.

[Martinski4GitHub]

@ExtremeFiretop,

Since I saw your post in the SNB Forums about the next 1.3.10 production release in preparation for the future 1.4.0 WebGUI release, this evening I decided to run some tests & validate the update/migration process. As a result, I made some changes to have a "smooth transition" to the newer version and remove the need to have an "extra" parameter for users to remember.

Whenever you have time, please review and validate this PR in conjunction with PR #404 created for the 1.4.0 WebGUI version. Both sets of PR changes must be installed and available together to test & validate the results of the update/migration process.

[ExtremeFiretop]

@ExtremeFiretop,

Since I saw your post in the SNB Forums about the next 1.3.10 production release in preparation for the future 1.4.0 WebGUI release, this evening I decided to run some tests & validate the update/migration process. As a result, I made some changes to have a "smooth transition" to the newer version and remove the need to have an "extra" parameter for users to remember.

Whenever you have time, please review and validate this PR in conjunction with PR #404 created for the 1.4.0 WebGUI version. Both sets of PR changes must be installed and available together to test & validate the results of the update/migration process.

Tested by going from 1.3.10 to 1.4.0 without issue.
Here is the result:

And I confirmed the WebUI loaded as expected with the expected values.
Merged both PRs!