Add migration and new schema version for resource_string

[phekmat]

This should resolve the issues with forcing a new resource described in the comments of #22

[apparentlymart]

Thanks for working on this follow-up fix, @phekmat!

This looks good to me. I have one bit of feedback inline, just to handle this cautiously for anyone who is already using this feature in v1.3.0.

[apparentlymart]

Because we've now shipped a version where these did exist in schema version 0, I think for safety we need to handle these conditionally so that we don't inadvertently cause further problems for people who have already applied changes with the v1.3.0 release.

I think it should be sufficient to just apply this change conditionally only if the attribute is not already set:

	if v := is.Attributes["min_special"]; v == "" {
		is.Attributes["min_special"] = "0"
	}

This would ensure that we don't overwrite any nonzero values that might have been inserted by users already trying to use the new feature with v1.3.0, which would then cause another forced replacement for those users.

[phekmat]

Good catch. Done

[catsby]

👍 thanks!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.