Enable type-scoped Versioning Behavior for workflows

[antlai-temporal]

Versioning-3 introduces behavior annotations for workflows that could change what Build ID will be used for a workflow next task.

The current API is programmatic, and requires invoking SetVersioningBehavior() during the first workflow task. This gives extra
flexibility for dynamic workflows but can be error-prone.

This issue suggests an alternative approach which associates a default behavior to a workflow type, using a new option for workflow registration.

Describe the solution you'd like

Add the option DefaultVersioningBehavior to workflow.RegisterOptions, providing a default behavior for all workflows of a particular type that do not use the programmatic API.