Refresh bug on graph

[Hubert-Szczepanski-SAP]

What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

[andreaskienle]

I've noticed this loading state behavior isn't just limited to the graph - it's also affecting the provider config table, which briefly shows a loading state during data reloads.

SWR already differentiates between isLoading (for the initial fetch) and isValidating (for subsequent fetches like polling). It looks like our ⁠useProvidersConfigResource hook might be setting ⁠isLoading to ⁠true for every fetch operation which causes the problem.

Could you take a look at this? I think we could improve the user experience by updating ⁠useProvidersConfigResource to only return ⁠isLoading: true during the initial fetch, following SWR's pattern. Checking this in the Graph component doesn’t feel right.