Use typedef for common types to make docs more concise

[peterflynn]

For example:

• @param {!{line:number, ch:number}} foo -->
  @param {!TextPos} foo
• @param {!{from:!{line:number, ch:number}, to:!{line:number, ch:number}} foo -->
  @param {!TextRange} foo

Not sure if there are any other types common enough to warrant this treatment, but those two alone would be a huge bang for the buck.

"Providers" in QuickOpen, Code hints, & CodeInspection might be other good candidates.

Need to:

• Verify that this work ok in apify
• Decide in what module to declare typedefs that are this general & widely-used

[redmunds]

This would help a lot in Editor.js for types such as:

@return {Array.<{selectionForEdit: {start:{line:number, ch:number}, end:{line:number, ch:number}, reversed:boolean, primary:boolean},
         selectionsToTrack: Array.<{start:{line:number, ch:number}, end:{line:number, ch:number}, reversed:boolean, primary:boolean}>}>}

[JeffryBooher]

@peterflynn I filed this card as we discussed yesterday in the find show index pr https://trello.com/c/xlOWyH2v

[ingorichter]

What a simplification for writing function/method docs.