the search pair function almost stalls my decently powerful macbook pro on really long lines, could be annoying because of minification etc.this function just makes it backwards compatible in old vim versions or builds without this feature

* prevent repeated calls of searchpair

```
var magicWords = ['abracadabra', 'gesundheit', 'ventrilo'],
  spells = {
    'fireball': function() {
      setOnFire()
    },
    'water': function() {
      putOut()
    }
  },
  a = 1,
  b = 'abc',
  etc, somethingElse
someFunc(param1, param2,
  param3, param4)
```
at the line which starts with a curly brace followed by a comment this was added for traversing the comma less property lines, however this only needs to be called once.this improves performance when using the endline operator style

an operator would previously  create an unnecessary indent when following a line which was the first of a list of block enclosed items, e.g. a array, function call, or object
before:
```
      vardefaultModules = {
        'http:': http
          ,'https:': https
      }
```
after:
```
      vardefaultModules = {
        'http:': http
        ,'https:': https
      }
```

looking at how the line found with searchpair starts
after:
```
    var protocol = defaultModules = {
      'http:': http
      ,'https:': https
    }
      ,htpModles = slf.htpModules || {}

    console.log()

Currently in a class definition, you can actually have a method called
`get`.  However with our match of `get` `set` and `static` as keywords,
we broke the ability to properly support those method names.  This
should fix those cases.

* working detection of object properties

the previous method is likely slower and doesn't really work

* fun args supported

also add support for func args

i don't know if this actually makes very much sense

```
10
  ..toString()
```
is invalid

* Re-organized a couple things
* Added some TODO comments to remind myself what needs to be done

I truly believe this has no place in a JS syntax file...

* Checked all aspects of jsExpression - In preparation for it to be
  properly used
* Code style tweaks - contained is such an important option, ensuring
  it's always first

With the refactoring of jsExpression, I was able to add a ton of finer
granularity to various new region types.

Current new regions:

* jsObject
* jsArray
* jsParenIfElse
* jsParenRepeat
* jsParenSwitch
* jsClassBlock
* jsBlock
* jsSwitchBlock
* jsTernaryIf

I think this is actually in a really good place. It seems to work well
in my test phaser.js file

Trying to make argument order more uniform

I don't think it needs to be a region, and infact incurs some annoying
complexity if so

There is one caveat right now, to properly support it, we sort of
require semicolons. Not sure if this is something people will be happy
with or not...

Because it's not ALWAYS an array

We can use this as a test. By unlinking it, it shouldn't ever have any
color theme associated with it, and if people complain, they can still
highlight it. Otherwise if we hear no complaints after a while, we just
pull it completely.

It's now technically a statement

* Fixes to jsSpreadOperator
* Added fold to jsObject
* Organized fold/extend arguments better

This fix may actually work out for us when using jsClassValue. There
still are some cases where it could be tripped up, for example on multi
line equations and stuff, but for the most part I think it should do the
trick.

This should help with errant detection in files that use Flow. It also
makes things safer so when typing out a ternary expression, you don't
get weird flickering of major syntax region changes.