Update OpenCollar - rlvex.lsl

Wow, I must say that this is one of the most extensive overhauls I've done in a while. I hope that users like the changes, and crossing fingers for no major bugs. So, here's the list of chat commands (some totally new, most re-formatted for ease of use)...
--- script is linked at the bottom of this card. As usual, please report any bugs ASAP to Joy Stipe. Very important with this one, as there are major changes in the script.
Recommend: make a copy of your collar, and set one in a safe place, as a backup in case of bad bugs
Delete the "OpenCollar - rlvex" script from your worn collar, then insert the new... then, of course, PLAY! Stretch it, kick it, tie it up and whip it!

First, the "exception" to the coming "rule": <prefix>menu exceptions - brings up the rlvex primary sub-menu

All other commands must begin with <prefix>ex - this will let the script know that the command is for it.

runaway/reset is the only command that a wearer can use, unless also a primary owner. ALL other commands require primary owner auth.

<prefix>ex owner - bring up the owners' exceptions menu (settings for all pri-owners)
<prefix>ex secowner - bring up the secowners' exceptions menu (settings for all secowners)
<prefix>ex other - bring up the list of "others", selecting a name brings up the exceptions sub-menu for that person
<prefix>ex add - scans & brings up the add-other menu; will notify of no avatar in range if no one is within 10m

---- all below can use uuid OR Legacy Name (case sensitive) ----

******* new chat command ******
<prefix>ex add Joe Resident  - add Joe Resident to others list -- added names will appear in the others sub-menu

---- below can be strided ----

<prefix>ex Joe Resident:defaults - will remove Joe Resident from the others list (default exceptions will then apply for his status as owner/secowner/other)
<prefix>ex Joe Resident:recvim=enforce,sendim=exempt  - set Joe Resident's exceptions to enforced recvim & exempted sendim
    - valid entries: sendim, recvim, recvchat, recvemote, tplure, or accepttp.
    - valid settings: n, add, enforce ... y, rem, exempt

- striding - use commas to separate settings for a user, and use colons to separate users EX: jrex Joe Shmoe:recvim=exempt:Jane Doe:sendim=enforce,recvim=exempt
- You may also still use uuids, if you prefer, though my belief is that most will prefer to use names :-D
- once a name is added to the list, it will remain there (and appear in the others sub-menu) until their settings are changed to "defaults" (via menu or chat)
- IF an avatar is specified with settings, before they have been added to the list: they will be added automatically
    - if name is used, Name2Key will attempt to get their uuid. If that fails, the user (who gave the command) will be notified that it failed. If successful, the user will be notified of success.
    - if uuid is used, the script will request the agent's name. Again, a fail or success notice will be sent to the command-issuer.
- IF you enter a strided set of commands for more than one user, the commands WILL process in the order entered, skipping failed additions along the way
    - You will not need to re-enter a set of commands just because one user-add fails, though you will have to re-enter command for that user...
        verify their case-sensitive legacy name or key before doing so, to save headache
    - remember, you will be notified if the script fails to fetch a key or name.