Per some customer feedback, this PR relaxes some of the constraints when creating template versions via thecoderd_template resource. Previously, each update of the resource required that at least one of the versions in theversions list had theactive attribute set to true.

This constraint is now only required when:

1. Creating the resource, as every template must have an active version.
2. It's not clear what template version should be set as active.
   • This occurs when the currently active version is marked as inactive, but no changes are made to the contents of the version (and no version would be created).

Examples of these cases can be seen in the tests.

With this, a workflow that involves:

• Marking an active version in the list as inactive
• Pushing it a few times via the provider
• And then finally marking it as active

is now possible with just a single item in the list.