Use newly compiled winloop.loop.Future objects on DNS related calls

[Vizonex]

What do these changes do?

These changes start whittling down on known bottlenecks between interpreter level and compiled level code.
The less the interpreter is needed the better the outcome.

For now winloop.Loop.Future remains internal core component to compete with rsloop's evolving speeds I always encourage friendly competition because it gives me a wakeup call.

In a later update like maybe 0.8.0 winloop.Loop.Future will be exposed at the user-level via loop.create_future which is my current objective once all internal level code is optimized with this new object.

Are there changes in behavior for the user?

DNS Tests take 1.91 seconds instead of 5-7 seconds more than sufficient to not needing c-ares yet.

Is it a substantial burden for the maintainers to support this?

Nope, in fact it does the opposite.

Related issue number

See: #164
Closes #80

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes

[Vizonex]

I'm starting to see 3 minute benchmarks for testruns. This makes me very happy :)

Keep in mind these tests used to take around 7-8 minutes on bad days.

[Vizonex]

TODO: (Vizonex) Improve 3.14t's lag. (Probably a reference bug of some kind. Improving NameInfo and AdderInfo would change this. I was thinking about trying C Callbacks.)