Report error if exports or require is used for declaration name in external module

Fixes #63
Negative test cases for collision of export and require declaration names
Do not emit references in generated declaration files if the --noresolve flag was set. This fixes a crash in the compiler when generating declarations with /// reference and noResolve
Merge pull request #569 from Microsoft/collisions

Report error if exports or require is used for declaration name in external module
add negative test for invalid references and declaration emit
Use double quotes in declaration file's reference path generation so that quotes in file name wouldnt affect reference resolution

Fixes #474
Merge pull request #605 from Microsoft/quotesInDeclarationFile

Use double quotes in declaration file's reference path generation
Add numeric indexer to HTMLElementCollection
Deferred type checking of function expressions to support circular definitions.
Accepting new baselines.
respond to code review remarks and reverted tryResolveScriptReference to resolveScriptReference
Merge branch 'master' into emitDeclarationWithNoResolve
Merge pull request #599 from Microsoft/emitDeclarationWithNoResolve

Do not emit references in generated declaration files if the --noresolve flag was set
Merge pull request #610 from Microsoft/circularFunctionExpressions

Circular function expressions
Merge pull request #609 from Microsoft/HTMLElementIndexer

Add numeric indexer to HTMLElementCollection
Properly report errors for failed type assertions
Fix incremental parsing bug due to non invalidating cached data in nodes.
Merge pull request #620 from Microsoft/incrementalParsingBug

Fix incremental parsing bug due to non invalidating cached data in nodes...
Conformance coverage for spec change #589
Merge pull request #618 from Microsoft/typeAssertionErrors

Properly report errors for failed type assertions