TISTUD-4173:JS Content Assist: access operator closes content assist menu

The following changes were made 

1. Activate the trigger character "." in Java script content assist 
2. Accord highest relevance to exact matches so that sorting places them on top.
3. Change proposal name sorting to ascending alphabetical order .. eg: foo,fooa,Fooa,Foo will be sorted to foo,Foo,fooa,Fooa when CA is triggered through ctrl+space
4.Modified tests to reflect new sorting 

So maybe I'm being super nuts about this, but I'm not sure which ordering you're looking to emulate here. There are some subtle difference in combining the comparisons as you do here. I whipped up a quick class to demonstrate what each variation gave us.  It's not evident to me which version is preferable, but if I had to guess it'd be shortest first, lowercase beats uppercase when they match ignoring case. (so, combination of compares for descending; compareToIgnoreCase for ascending in the examples). I don't know if we also eventually reverse the list, which would make it even wackier.

```
Descending
abc, aBC, ABc, ABC, AbC, abC, Abc, aBc <- original
abc, abC, aBc, aBC, Abc, AbC, ABc, ABC <- compareTo
abc, aBC, ABc, ABC, AbC, abC, Abc, aBc <- compareToIgnoreCase
abc, abC, aBc, aBC, Abc, AbC, ABc, ABC <- combination

Descending
foo, Fooa, fooa, Foo <- original
fooa, foo, Fooa, Foo <- compareTo
Fooa, fooa, foo, Foo <- compareToIgnoreCase
fooa, Fooa, foo, Foo <- combination

Ascending
foo, Fooa, fooa, Foo <- original
Foo, Fooa, foo, fooa <- compareTo
foo, Foo, Fooa, fooa <- compareToIgnoreCase
Foo, foo, Fooa, fooa <- combination
```