dnf package resource version comparison failures, part 3

[epilatow]

As a follow up to #10950, I found another dnf faiulre for :purge and :remove package resources, also caused by a comparison between current_version and new_version. Here's some chef debug output for an rpm which is failing to be removed:

Processing dnf_package[fb-mysql-server-5.6.35-202010141616.prod] action purge (fb_mysql::fb_mysql_server_rpm line 85)
Providers for generic dnf_package resource enabled on node include: [Chef::Provider::Package::Dnf]
Provider for action purge on resource dnf_package[fb-mysql-server-5.6.35-202010141616.prod] is Chef::Provider::Package::Dnf
sending '{"action":"whatinstalled","provides":"fb-mysql-server-5.6.35-202010141616.prod"}' to python helper
got 'fb-mysql-server-5.6.35-202010141616.prod 0:5.6.35-202010141616.prod x86_64' from python helper
parsed fb-mysql-server-5.6.35-202010141616.prod-0:5.6.35-202010141616.prod.x86_64 from python helper
sending '{"action":"whatinstalled","provides":"fb-mysql-server-5.6.35-202010141616.prod","version":"5.6.35","release":"202010141616.prod"}' to python helper
got 'fb-mysql-server-5.6.35-202010141616.prod 0:5.6.35-202010141616.prod x86_64' from python helper
parsed fb-mysql-server-5.6.35-202010141616.prod-0:5.6.35-202010141616.prod.x86_64 from python helper

It's worth pointing out that this package has its version and release information also embedded into its name. The removal fails when removing_package? calls have_any_matching_version? because equality comparisons fail for the following version strings:

current_version_array: ["0:5.6.35-202010141616.prod.x86_64"]
new_version_array: ["5.6.35-202010141616.prod"]

[epilatow]

The failure mode is that the package doesn't get removed.