Migrate dns_ptr_record resource to dns_ptr_record_set

[verejoel]

There is already a pull request (#105) to add a new dns_ptr_record_set resource. Here I have performed a migration from the original resource to the new resource, as I don't see the point of having two ptr resources.

This would fix #93

[detro]

Hello @verejoel,

unfortunately an implementation like this will guarantee breaking existing TF configurations using the resource. So, it's not something we can accept.

The topic of "should we support handling PTR records with multiple Answers" is being addressed in #105 (that you also pointed at), so we will continue there.

Thanks anyway and I hope you understand the issue of not being able to just rename a resource.

[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.