We occasionally have infrequent or one-off background maintenance tasks we wish to run in the server. Currently we typically need to register these with some existing service that runs periodically and requires that service to check whether we have any such tasks waiting. Alternatively we sometimes create a new background service for each such type of task (a dedicated thread, either raw or via PeriodicJobRunner), which runs into issues of thread proliferation.

As an alternative, we can create a general-purpose task queue that processes these infrequent tasks when they come available.

At least to begin with, the queue will be focused on processing light-weight tasks, and is not meant to replace any existing thread pools that we use for heavy processing (e.g. index builds).