Paul Reardon

Feature #3111 Update Distributed Lock to return and accept a LockId

**Is your feature request related to a problem? Please describe.** Since Brighter 9.8.0 there has been an `IDistributedLock` that is used to ensure that the Outbox Sweeper isn't running concurrently...

The way in which the outbox sweeper works is to grab the top x dispatched messages and attempt a dispatch every y number of seconds. This problem with this is...

It appears that everytime the `IServiceBusClientProvider` is used to `GetServiceBusClient` of `GetServiceBusAdministrationClient` a new instance of the clients are newed up. **Describe the solution you'd like** I would like this...

A guide should exist to guide users to Migrating from v9 to v10

Currently Brighter creates a Scope around the Command Handler, we need this to be around the Request Handler

Functionality should exist to be able to set a Default Message Mapper with the ability to specify overrides for Individual Message Types. Also Brighter should include a Default Message Mapper...

This will allow users will the public role to use locking instead of requiring dbo

Outbox Sweeper effectively ignores the distributed lock due to the sweeping being done on a background thread

1

### Describe the bug In the timed outbox sweeper we use a Locking provider ``` c# var lockId = _distributedLock.ObtainLockAsync(LockingResourceName, CancellationToken.None).Result; if (lockId != null) { s_logger.LogInformation("Outbox Sweeper looking for...