Prevent the use of NSB configuration APIs that aren't applicable to serverless environments

[kbaley]

The package provides access to the NServiceBus EndpointConfiguration for advanced configuration scenarios. Not all of these configuration options work as expected in an Azure Functions context. Version 4.3.0 of the package introduces a new Roslyn analyzer that detects the use of these configuration options and causes compile-time warnings and errors.

See Roslyn analyzers for Azure Functions in the documentation for information about the affected configuration options.

Describe the suggested improvement

For the AzureFunctions.Worker.ServiceBus package, much of the NServiceBus configuration API has been moved behind the AdvancedConfiguration API to keep users focused on the most common ones. Some of these APIs aren't applicable to a serverless environment but there's nothing stopping someone from using them, sometimes with unpredictable results. Some examples:

• UseTransport
• PurgeOnStartup
• DefineCriticalErrorAction
• SetDiagnosticsPath
• LimitMessageProcessingConcurrencyTo
• MakeInstanceUniquelyAddressable
• OverrideLocalAddress
• RouteReplyToThisInstance
• RouteToThisInstance

Plus some Azure Service Bus transport properties:

• MaxAutoLockRenewalDuration
• PrefetchCount
• PrefetchMultiplier
• TimeToWaitBeforeTriggeringCircuitBreaker

We should implement a way to ensure these APIs aren't used in production.

Additional Context

A spike for a Roslyn analyzer that throws an error when certain APIs are used can be found here.

• Prevent the use of NSB configuration APIs aren't applicable to serverless environments NServiceBus.AwsLambda.Sqs#253
• Prevent the use of NSB configuration APIs that aren't applicable to serverless environments NServiceBus.AzureFunctions.Worker.ServiceBus#302