Optimize Object Explorer Data Fetching Using React Query

[adity1raut]

Description

This Pull Request improves the performance of the Object Explorer page by implementing React Query for fetching and caching resource kinds, namespaces, and filtered resources.
Previously, every filter change or page refresh triggered multiple backend API requests, leading to unnecessary load and slower UI performance.

Implemented useQuery for resourceKinds and namespaces with caching and 5-minute staleTime
Added useQueries to fetch filtered resource data in parallel based on selected kinds and namespaces
Introduced smart query keys to reuse cached data and reduce repeated backend calls
Enabled global refetch support with refetchResourceData
Improved loading, error handling, and filtering management
Reduced redundant backend calls and improved responsiveness

Related Issue

Fixes #2123

Changes Made

• Updated ...
• Refactored ...
• Fixed ...
• Added tests for ...

Checklist

Please ensure the following before submitting your PR:

• I have reviewed the project's contribution guidelines.
• I have written unit tests for the changes (if applicable).
• I have updated the documentation (if applicable).
• I have tested the changes locally and ensured they work as expected.
• My code follows the project's coding standards.

Screenshots or Logs (if applicable)

Additional Notes

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign onkar717 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubestellar-prow]

Hi @adity1raut. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[adity1raut]

PTAL @alokdangre

/cc @clubanderson

[clubanderson]

/ok-to-test

[SakshamDutt]

@adity1raut Good Work!

[adity1raut]

/cc @kunal-511 @MAVRICK-1