[chirp_devel] [h777] Fix some settings not taking effect on Baofeng 888 and variants

[Dan Smith]

>>> I have another datapoint, external to CHIRP and Radioddity. miklor.com has 2 software versions listed that can program the BF-888 class radio. 
>>> One version is listed as "BF-888S v1.05" and the other is listed as "ZT-V68 2007"
>>> 
>>> - The "v1.05" software writes the data blocks in the same order as CHIRP, also using only the "W" commands.
>>> - The "ZT-V68" software, writes the data blocks in a different order than CHIRP (as reflected by my patch) and uses a "Y" command for those middle blocks.
>>> 
>>> I found through testing that:
>>> - The "Y" command is not strictly necessary. 
>>> - Using all "W" commands works, as long as the order (_ranges variable in h777.py) is updated (as seen in my patch).
>>> - Using the "Y" commands with the original order (unmodified _ranges variable) does not work.

Tony, have you been seeing the traffic on this bug?

https://chirp.danplanet.com/issues/7067

I believe my fears of introducing a regression came true and that these folks are hitting the problem.

I really don't want to have to register a "BF-888 (Old)" radio driver in CHIRP, but that might be the simplest thing to do. Would love to hear some analysis from you on this. All of mine are apparently the same vintage so I can't really test much.

--Dan