xNewAdapterName output misleading when Adapter Not Found

[PlagueHO]

If the xNewAdapterName resource is used to rename an adapter using the name where an adapter with the existing or new name can't be found then a misleading error message will be shown.

[PlagueHO]

@johlju, @ChrisLGardner - I've found a few more bugs in this (exposed when I extended integration tests to cover a simple rename using name only). So I've fixed those as well.

I've improved the log information as well and extended the integration and unit tests to provide better coverage of these scenarios.

The resource can now be correctly used to rename an adapter by just identifying it by name. But this isn't the primary user story that drove this. If you know the adapter name already, then renaming it isn't really that useful (but it'll work).

The primary user story that this should address is when you don't know the adapter name in the OS - you only know various parameters of the adapter (e.g. MAC Address, Driver) and therefore need to rename it so that that all other resources have a known name they can reference.

For example:

        xNetAdapterName RenameNetAdapterCluster
        {
            NewName        = 'Cluster'
            MacAddress     = '9C-D2-1E-61-B5-DA'
        }

This will work fine - but it's not really the primary purpose:

        xNetAdapterName RenameNetAdapterCluster
        {
            NewName        = 'Cluster'
            Name      = 'Ethernet 1'
        }