Fix idempotency issues with non-HTTP IIS site bindings

Sites using non-HTTP protocols (net.pipe, net.tcp, net.msmq,
msmq.formatname) were reapplied on every Puppet run due to unreliable
sorting and hash order sensitivity in binding comparison.

Replace custom sorting with set-based comparison to ensure identical
bindings are recognized regardless of array order or hash property order.

Resolves: Continuous configuration drift for non-HTTP protocol bindings

Author: DarkArc-Github

lib/puppet/type/iis_site.rb

@@ -5,7 +5,6 @@
 require_relative '../../puppet_x/puppetlabs/iis/property/hash'
 require_relative '../../puppet_x/puppetlabs/iis/property/path'
 require_relative '../../puppet_x/puppetlabs/iis/property/authenticationinfo'
-require_relative '../../puppet_x/puppetlabs/iis/bindings'
 
 Puppet::Type.newtype(:iis_site) do
   @doc = "Allows creation of a new IIS Web Site and configuration of site
@@ -156,17 +155,8 @@ def insync?(is)
       value
     end
 
-    def should
-      PuppetX::PuppetLabs::IIS::Bindings.sort_bindings(super)
-    end
-
-    def should=(values)
-      super
-      @should = PuppetX::PuppetLabs::IIS::Bindings.sort_bindings(@should)
-    end
-
     def insync?(is)
-      PuppetX::PuppetLabs::IIS::Bindings.sort_bindings(is) == should
+      (is || []).to_set == (should || []).to_set
     end
   end