Add analyzers that help prevent developer gotchas

[WhitWaldo]

Describe the feature

This is intended more as a parent issue to track progress for individual analyzers, but the goal is that we reduce some of the opportunities for developers to inadvertently misconfigure things that we might catch at build time and reduce runtime exceptions. Here's a short and evolving list of opportunities here:

• Actor cross-serialization errors Ensure that when developers retain DataContract serialization or opt into JSON-based serialization, they're not inadvertently cross-serializing in a way that breaks the serializers and deserializers for either approach.
• Actors Identify actors that are referenced, but not registered in DI
• Actors When AddActors is found, validate that MapActorsHandlers is in place
• Workflows Identify workflows and workflow activities that are referenced, but not registered in DI
• Workflows Ensure that during startup, those resources that require a app.UseX() have it specified in Program.cs
• PubSub When programmatic subscriptions are used (e.g. WithTopic or a Topic attribute), validate that MapSubscribeHandler is in place** - thanks to @ngruson for the idea

Release Note

RELEASE NOTE: ADD Analyzers to help prevent runtime errors

[jev-e]

I'd be interested in looking at this; although partially motivated by self improvement as my knowledge of Roslyn analysers isn't super strong, but an area I'd like to improve.