v4.1.1

This release fixes the following bug:

When upgrading Terraform provider from v3.3.2 to v4.1.0, users encounter a "cannot update options [toolkit_path]" error. This happens because toolkit_path moved from being a top-level parameter to a nested parameter within the hosts block, but the provider doesn't handle this migration gracefully.

Solution
Implement a silent migration strategy for the toolkit_path and ignore_tag_changesparameter:

Testing

• Validated with v3.3.2 → v4.1.1 upgrade scenario
• Confirmed terraform plan shows "No changes" (silent migration)
• Verified backward compatibility with existing environments
• Tested update-in-place functionality works without errors

Impact

• Users: Seamless upgrade path from v3.3.2 to v4.1.1 without breaking changes