message: Navigated link for constraint errors
  Shows removing parseLink is better because fluent test matches navigate link tests. They don't throw when building the url, only throw when navigating link. Before fluent threw when building url
diff: @@ -6899,7 +6899,8 @@ describe('Navigation Data', function () {
  describe('Fluent Navigate', function() {
  it('should throw error', function() {
  - assert.throws(() => stateNavigator.fluent().navigate('s', individualNavigationData), /The Url .+ is invalid/);
  + var link = stateNavigator.fluent().navigate('s', individualNavigationData).url;
  + assert.throws(() => stateNavigator.navigateLink(link), /The Url .+ is invalid/);
  });
  });
  });
  @@ -6939,7 +6940,8 @@ describe('Navigation Data', function () {
  describe('Fluent Navigate', function() {
  it('should throw error', function() {
  - assert.throws(() => stateNavigator.fluent().navigate('s', arrayNavigationData), /The Url .+ is invalid/);
  + var link = stateNavigator.fluent().navigate('s', arrayNavigationData).url;
  + assert.throws(() => stateNavigator.navigateLink(link), /The Url .+ is invalid/);
  });
  });
  });
  