Highlight `NOTE` to mention in documentation or JSDoc

Given the following code

```javascript
class Foo {
  bar;

  baz = 'biz';
}
```

The `baz` is properly matched as a `jsClassProperty` but `bar is
`jsClassBody`. The regex for `jsClassProperty` was requiring the `=`
that followed the property name. The changes allow value less
properties by allowing either `;` or `=` to follow the name.

As of Node 13.2.0, the `--experimental-modules` flag was removed making
usage of ES modules available by default. As part of the Node ES modules
support, they allow a package to define their default module type (which
is how `.js` files are interpretted) and also allow using either `.cjs`
or `.mjs` to explicitly declare a given file is of one format or the
other.

We already had the `.mjs` extension supported so this adds `.cjs` to
round out support for Node's ES module system.

References:

* [v13.2.0 release post unflagging `--experimental-modules`](https://nodejs.org/en/blog/release/v13.2.0/)
* [v14 documentation of ES Modules](https://nodejs.org/api/esm.html)

…#1230)

Fixes pangloss#1232

I am not going for a super accurate fix, just enough to not break syntax
highlighting in a valid use case

Add syntax highlightling to WeakRef as defined in tc39/proposal-weakrefs

Add syntax highlighting to BigInt literals and to the BigInt built-in object as defined in tc39/proposal-bigint.

Fixes incorrect highlighting of blocks as objects.

Added a tilde to the jsDocParam syntax match to support jsdoc3 namepaths style (i.e. when creating a typedef for an inner member).
See https://jsdoc.app/tags-typedef.html

Co-authored-by: Jonathan Halchak <[email protected]>

…ngloss#1244)

…ring paste in some terminals (pangloss#1258)