feat(bullmq): improvements
### Is your feature request related to a problem? Please describe.

Hey again,

i'm currently looking into the `bullmq` package and think i found some stuff to optimize. I can do this and create a PR, but before i would like to talk about what i would change:

1. Remove `disableWorker` from config - this is unused and not needed because of `workerQueues`
2. Deprecate `defaultJobOptions` and add `defaultQueueOptions` - currently you can only set the `defaultJobOptions` option for a queue, while a queue itself has more options to configure
3. Add queue specific options - In case you want to configure two queues differently, you can not do this atm. I thought to use a type like `queueOptions: Record<string, QueueOptions>`, where the key should be the queue name?
4. Same goes for workers. You can't configure them atm, so i would add a `defaultWorkerOptions` applied to every worker and `workerOptions` (like in 3.) to configure some workers specifically
5. Also i would like to add some listeners to the workers as described in the bullmq docs like:

```ts
worker.on('completed', (job: Job<DataType, ResultType, NameType>, result: ResultType) => {
  // add some logic...
});

worker.on('failed', (job: Job<DataType, ResultType, NameType> | undefined, error: Error) => {
  // add some logic...
});

worker.on('error', (failedReason: Error) => {
  // add some logic...
});
```

users should be able to add these accordingly to their needs, im unsure about what the best way to handle this is. Any recommendations? 🤔

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

### Acceptance criteria

_No response_