Move resolveRelativeUri into front_end.

Move resolveRelativeUri into front_end.

Note: I removed the exception wrapping code as part of the migration.
Rationale: this function performs a small task and has been operating
successfully for a long time; removing the exception wrapping code
avoids making front_end dependent upon AnalysisException and
CaughtException at this time.  In the unlikely event that an exception
occurs in this function, we still have many avenues available for
tracking down the problem: examine the stack trace of the exception,
isolate a repeatable test case (if the exception happened in
e.g. command-line analyzer), or reproduce the exception from file
state information recorded by the AnalysisDriver (if the exception
happened in analysis server).

R=scheglov@google.com

Committed: https://github.com/dart-lang/sdk/commit/d8fc3630cff055376f915422842f3c1bb503cb7f

[Paul Berry, 2017-01-30 22:48:39]

paulberry@google.com changed reviewers:
+ scheglov@google.com

[scheglov, 2017-01-30 22:57:46]

LGTM

[Paul Berry, 2017-01-30 23:06:02]

Description was changed from

==========
Move resolveRelativeUri into front_end.

Note: I removed the exception wrapping code as part of the migration.
Rationale: this function performs a small task and has been operating
successfully for a long time; removing the exception wrapping code
avoids making front_end dependent upon AnalysisException and
CaughtException at this time.  In the unlikely event that an exception
occurs in this function, we still have many avenues available for
tracking down the problem: examine the stack trace of the exception,
isolate a repeatable test case (if the exception happened in
e.g. command-line analyzer), or reproduce the exception from file
state information recorded by the AnalysisDriver (if the exception
happened in analysis server).
==========

to

==========
Move resolveRelativeUri into front_end.

Note: I removed the exception wrapping code as part of the migration.
Rationale: this function performs a small task and has been operating
successfully for a long time; removing the exception wrapping code
avoids making front_end dependent upon AnalysisException and
CaughtException at this time.  In the unlikely event that an exception
occurs in this function, we still have many avenues available for
tracking down the problem: examine the stack trace of the exception,
isolate a repeatable test case (if the exception happened in
e.g. command-line analyzer), or reproduce the exception from file
state information recorded by the AnalysisDriver (if the exception
happened in analysis server).

R=scheglov@google.com

Committed:
https://github.com/dart-lang/sdk/commit/d8fc3630cff055376f915422842f3c1bb503cb7f
==========

[Paul Berry, 2017-01-30 23:06:03]

Committed patchset #1 (id:1) manually as
d8fc3630cff055376f915422842f3c1bb503cb7f (presubmit successful).