feat(web): adminRequests cache key + staleTime polish

- qk.adminRequests defaults to status='all' when no filter is set; the unfiltered
  endpoint returns every status, so caching it as 'pending' was a latent mismatch.
- 60s staleTime on lidarrConfig + myRequests — both are session-stable enough
  that refetching on every consumer-page mount produced needless flicker.

web/src/lib/api/admin.test.ts

@@ -215,8 +215,11 @@ describe('qk admin keys', () => {
   test('lidarrRootFolders key', () => {
     expect(qk.lidarrRootFolders()).toEqual(['lidarrRootFolders']);
   });
-  test('adminRequests key defaults to pending when status omitted', () => {
-    expect(qk.adminRequests()).toEqual(['adminRequests', { status: 'pending' }]);
+  test('adminRequests key uses "all" when status omitted', () => {
+    // listAdminRequests sends no status param when called without one (returns
+    // every status), so the cache key must distinguish that from any specific
+    // status — otherwise an unfiltered call would falsely cache as `pending`.
+    expect(qk.adminRequests()).toEqual(['adminRequests', { status: 'all' }]);
   });
   test('adminRequests key includes the status filter', () => {
     expect(qk.adminRequests('approved')).toEqual([