daemon: Remove unneeded error wrapping in verifyNetworkingConfig
**- What I did**

Related to:

- https://github.com/moby/moby/pull/45906#discussion_r1280796908

This function is called by `daemon.containerCreate()` which is already wrapping errors coming from `verifyNetworkingConfig()` with `errdefs.InvalidParameter()`. So `verifyNetworkingConfig()` should only return standard errors.

**- A picture of a cute animal (not mandatory but encouraged)**

![](https://www.animalspot.net/wp-content/uploads/2014/08/Mandarinfish-Baby.jpg)

daemon/create_test.go
package daemon // import "github.com/docker/docker/daemon"

import (
	"testing"

	"github.com/docker/docker/api/types/network"
	"github.com/docker/docker/errdefs"
	"gotest.tools/v3/assert"
)

// Test case for 35752
func TestVerifyNetworkingConfig(t *testing.T) {
	name := "mynet"
	endpoints := make(map[string]*network.EndpointSettings, 1)
	endpoints[name] = nil
	nwConfig := &network.NetworkingConfig{
		EndpointsConfig: endpoints,
	}
	err := verifyNetworkingConfig(nwConfig)
	assert.Check(t, errdefs.IsInvalidParameter(err))
}

package daemon // import "github.com/docker/docker/daemon"

import (
	"testing"

	"github.com/docker/docker/api/types/network"
	"gotest.tools/v3/assert"
	is "gotest.tools/v3/assert/cmp"
)

// Test case for 35752
func TestVerifyNetworkingConfig(t *testing.T) {
	name := "mynet"
	endpoints := make(map[string]*network.EndpointSettings, 1)
	endpoints[name] = nil
	nwConfig := &network.NetworkingConfig{
		EndpointsConfig: endpoints,
	}
	err := verifyNetworkingConfig(nwConfig)
	assert.Check(t, is.Error(err, "no EndpointSettings for mynet"), "should produce an error because no EndpointSettings were passed")
}

Hm... yeah, so in _some cases_ I agree. But I also have seen quite some tests that continued passing, but were no longer testing what they were supposed to test, and now testing a completely unrelated error.

I guess the thing he wanted to avoid (and where I agree) is that we now could consider this error-message to be an API (it isn't). i.e., this test starting to fail if we re-phrase the error-message is ok; in that case the test needs updating.

^^ we've had cases where we thought we couldn't update the error-message because the test started failing.


So if that's a concern, we can still leave a comment in the assertion to make it more clear that it's not the exact format of the error-message that matters, but the _reason_ of the error; something like;

```go
assert.Check(t, is.Error(err, "no EndpointSettings for mynet"), "should produce an error because no EndpointSettings were passed")
``` 



