Fix SocketPoolConstants typo

[justmobilize]

I can't spell. Another user found a type in WIZnet, so also fixing it here

[dhalbert]

I am thinking that the superclass SocketPoolConstants is not really needed, since the native socketpool doesn't have it either. It would save space and time to just have the constants as class attributes in SocketPool.

[justmobilize]

@dhalbert I'm open to suggestions, but this is why the superclass was added. Since we are in the class, it's not defined and thus this line will error on import:

ignore the line number in the image, it's this one

[dhalbert]

I see. But what about something like this? This works:

class ConstantsTest:
    A = 1
    B = 2

    def f(self, a=A, b=B):
        pass

The unqualified name works.

This actually is more complicated. In CPython, AF_INET, etc. are defined at the module level, not inside the Socket class. I can't remember why we defined them as class constants in SocketPool instead of in socketpool.

[justmobilize]

Ahh, I can do a commination of both...

I'm assuming they are in SocketPool, since that's where they were when ESP32SPI was created and so when socketpool.SocketPool was created if followed suit?