Add Custom withRouteProps HOC for react-router-dom v6 migration

[anshgoyalevil]

Which problem is this PR solving?

• part of: Upgrade react-router-dom to latest version #1825

Description of the changes

• On our pathway to upgrade rrd to v6.x latest, we have to use custom withRouteProps HOC since rrd v6 doesn't support withRouter.
• With this change, we won't be able to access the history object anymore, and neither the other Route Props.
• This PR adds the custom useHistory() hook and provider to use the history object in our custom withRouterProps HOC.

Why this PR is necessary?

• This is a part of the upgrade process for rrd v6.
• Since there are a lot of breaking changes other than withRouter removal in rrd v6, this PR ensure that we migrate out codebase at v5 only as recommended by the react-router-dom team in their v5 to v6 migration guide

How was this change tested?

• Have manually checked every page. Everything is working as of now.

screen-capture.3.webm

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: yarn lint and yarn test

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Files	Coverage Δ
packages/jaeger-ui/src/components/App/Page.tsx	100.00% <ø> (ø)
packages/jaeger-ui/src/components/App/TopNav.tsx	94.44% <ø> (ø)
...aeger-ui/src/components/App/TraceIDSearchInput.tsx	100.00% <ø> (ø)
packages/jaeger-ui/src/components/App/index.jsx	100.00% <ø> (ø)
...components/SearchTracePage/SearchResults/index.tsx	86.15% <ø> (ø)
...ePage/TraceTimelineViewer/VirtualizedTraceView.tsx	96.95% <ø> (ø)
...es/jaeger-ui/src/components/common/UiFindInput.tsx	100.00% <ø> (ø)
packages/jaeger-ui/src/utils/useHistory.tsx	100.00% <100.00%> (ø)
packages/jaeger-ui/src/utils/withRouteProps.tsx	100.00% <100.00%> (ø)

📢 Thoughts on this report? Let us know!.