Parse - Bring in type and variable naming rules

Parse - Bring in type and variable naming rules

* We distinguish between type/class names and non-type identifiers
  by the format of the symbol.  This is something I've always wanted to
  do to enforce a little better readability for the code, but it also
  is a huge aid to the front-end parser which has far less context available
  to it than other languages might.  We can differentiate between (type)
  and (subexpression), for example.

  - Any symbol terminating in _t _u _p or _m is considered a type/class id.

  - Otherwise if it starts with a capital letter and all the alpha characters
    are not capitalized, it is a type/class id.

  - If all alpha characters are capitalized it is a constant identifier
    (not currently enforced).

  - Otherwise it is a non-type identifier.

* Examples:

  FUBAR_t	- type/class
  FUBAR		- constant identifier
  Fubar		- type/class
  fubar		- normal identifier

* Note that if you are used to a global variable starting with a capital,
  that is not allowed in Rune.  There are numerous reasons for this but
  mainly the problem, other than distinguishing types vs variables, is
  that the global might be referenced by a class path and in that context
  the capitalization can create a lot of confusion.