Expose MaxDeliveryCount with a default set to 100

[andreasohlund]

• Exposes the MaxDeliveryCount
• Defaulting MaxDeliveryCount to 100 since functions have dlq autoforwarding enabled by default
• Exposes ThrowOnMissingTopicWhenPublishing
• updates to the latest asb transport 6.3
• reuses logic to extract message id, headers and body to ensure transport and functions stay in sync

[DavidBoike]

Doesn't this statement conflict with the preset 100 for Serverless mode?

[andreasohlund]

Fixed, but I wonder if we have another issue.

@danielmarbach since the transport will only lower the default to 10 when the emulator is in use if a value isn't set we might need to bring that logic in here as well?

Or alternatively, always force the delivery count to 10 in the transport?

[andreasohlund]

Discussed with @danielmarbach, and we concluded that since the MaxDeliveryCount is now exposed, we can do nothing, and if users run in the emulator, they will get an exception and can then set it to 10 until MS fixes the issue with the emulator only supporting max 10

Alternatively, we could default to 10 (which is the default when using az, the portal, or the api), but that might be a bit too low? (ie if you do 10 immediate reties you would be dlq'd)