refactor(handler): cache active instances (#9008)

# Which Problems Are Solved

Scheduled handlers use `eventstore.InstanceIDs` to get the all active
instances within a given timeframe. This function scrapes through all
events written within that time frame which can cause heavy load on the
database.

# How the Problems Are Solved

A new query cache `activeInstances` is introduced which caches the ids
of all instances queried by id or host within the configured timeframe.

# Additional Changes

- Changed `default.yaml`
  - Removed `HandleActiveInstances` from custom handler configs
- Added `MaxActiveInstances` to define the maximal amount of cached
instance ids
- fixed start-from-init and start-from-setup to start auth and admin
projections twice
- fixed org cache invalidation to use correct index

# Additional Context

- part of #8999

internal/notification/handlers/notification_worker_test.go

@@ -877,16 +877,15 @@ func newNotificationWorker(t *testing.T, ctrl *gomock.Controller, queries *mock.
 			},
 		},
 		config: WorkerConfig{
-			Workers:               1,
-			BulkLimit:             10,
-			RequeueEvery:          2 * time.Second,
-			HandleActiveInstances: 0,
-			TransactionDuration:   5 * time.Second,
-			MaxAttempts:           f.maxAttempts,
-			MaxTtl:                5 * time.Minute,
-			MinRetryDelay:         1 * time.Second,
-			MaxRetryDelay:         10 * time.Second,
-			RetryDelayFactor:      2,
+			Workers:             1,
+			BulkLimit:           10,
+			RequeueEvery:        2 * time.Second,
+			TransactionDuration: 5 * time.Second,
+			MaxAttempts:         f.maxAttempts,
+			MaxTtl:              5 * time.Minute,
+			MinRetryDelay:       1 * time.Second,
+			MaxRetryDelay:       10 * time.Second,
+			RetryDelayFactor:    2,
 		},
 		now:     f.now,
 		backOff: f.backOff,