Update each entry to match PPCL editor help files
Update each entry to match PPCL editor help files

These changes were auto-generated from PPCL help--with some manual
tweaking. Although, some entries, like .SQRT., were previously
incorrect, most were fine, but they were changed anyway to match the
PPCL Editor help for the sake of consistency.

The hover.py file was changed to return keywords between dots, so
keywords like: .AND., .EQ., .ROOT., get looked up as: AND, EQ, ROOT,
which is why the .EQ. entry is now just "EQ".

I also tried striping ending digits, rather than creating an entry for
each of LOC1...LOC15/ARG1...ARG15. This way there would just be one
entry LOC/ARG for each, but I reverted back to including the trailing
number because I realized this could be misleading, given certain
programming styles. E.g. Some PPCL programmers are in the bad habit of
extending the $LOCx nomenclature beyond fifteen points by defining
them as local points, rather than giving local variables intelligible
names--e.g. LOCAL(LOC16, LOC17). This would incorrectly lead the help
to indicate these points are built-in local points. This approach also
caused problems with SECNDn and ALMCT2.

blandfbt/PPCL,semiamaurotic/PPCL