…ameter is semanticsally the same

The URI compare does not taking into account that query parameter may or may not be encoded, or the parameters' order can be different. However, they are all semantically the same. 

This pr makes PlatformRouteInformationProvider to take those into account when deciding whether it should push/replace the browser history entry.

PLUS: clean-up of all the unreachable stuff.

Related https://github.com/flutter/flutter/issues/100624

The goal is to make sure the engine can send a location string in either the existing format or a complete uri string to the framework, and the framework will still work as usual.

Migrate away from deprecated BinaryMessenger API

* Add getInheritedWidgetOfExactType to BuildContext

* Use the new API in all the places

* Fix doc error

* Review Changes

* Use `curly_braces_in_flow_control_structures` for `widgets`

* fix comments

* fix comments

* Fix crashes when current route parsing transactions are discarded

* refactor

* update

This reverts commit d056500b.

This reverts commit 31de052e.

This reverts commit e2490f29.

* Improve backbuttondispatcher

* update

* update

* fix analyzer

* addressing comments

* make takeprioirty recursive by default

* fix comment

* addressing comment

This removes the nullOk parameter from Router.of, and createsRouter.maybeOf. Router.ofnow returns a non-nullable value, and the Router.maybeOf returns a nullable value.