Angular does not currently include the non-fragment query portion
Of URLs in non-html5 $location mode. This commit merges the fragment
Query, if present, with the non-fragment query if it exists.

See#15856

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix.

What is the current behavior? (You can also link to an open issue here)
AngularJS's $location service treats URLs differently depending on whether or not the browser supports the HTML5 history API or requires the use of the hashbang mode. URLs should be parsed into the same object regardless of browser mode. In the current behaviour, query parameters are lost.

What is the new behavior (if this is a feature change)?
In non-HTML5 hashbang mode, the query parameters that appear prior to the fragment identifier (#) are copied into the fragment identifier before theparseAppUrl function is called. Therefore, the query parameters outside of the fragment are included in both html5 and non-html5 modes.

Does this PR introduce a breaking change?
Not really.

Please check if the PR fulfills these requirements

• [ x] The commit message follows our guidelines:https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
• [ x] Tests for the changes have been added (for bug fixes / features)
• [ x] Docs have been added / updated (for bug fixes / features)
  Note that docs are essentially added as part of the discussion in the GitHub issue$location does not parse query portion of URL correctly when in non-html5 mode. #15856

Other information:
None.