fix: url params should not propagate across pages

[vikrantgupta25]

Summary

Issue 1:

• dashboards list url params gets initialised with the wrong params since the DashboardsProvider is wrapped at the very top of the application.
• moved the initialisation to pick values from the url only when present on the Dashboards List page.
• added extra checks in place to default to updatedAt when the key is mismatched and order to descend

Issue 2:

• when on alerts list page if the order is set to undefined then after that navigating to the old logs explorer the order is retained.
• why? because it is being initialised in the reducer on load of the app. so moved the condition to only pick from the url on load if the user is present at the old logs explorer page else default it to desc as happening before.
• added extra checks in place to default to desc when the key is mismatched

Issue 3:

• the performance of rendering dashboard list page was very poor as the component was re-rendering around a 100 times.
• refactored the component for better performance.
• the search string was not getting updated in the URL.
• because of this re-renders we were unable to write proper unit test for the same.

Started adding test cases for the dashboards list page

Related Issues / PR's

Fixes :- #5394

Fixes :- #5448

Screenshots

NA

Affected Areas and Manually Tested Areas

• tested dashboard list page ( various use cases / set different sorts and goto details page and navigate back etc.)
• tested the url isolation issue with logs and dashboards

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>