winapi: rpcasync
raw: Regenerate with latest fbfrog
winapi: _bsd_types
winapi: inaddr
winapi: Expand socket/fd_set/etc. stuff into winsock[2]
winapi: bcrypt
winapi: ncrypt
winapi: winefs
winapi: winscard
raw: winapi: Translate headers as part of windows.h where needed

There's a lot of files that make up the Windows API headers, and it's not
clear which of them are intended to be included indirectly through
windows.h, or directly.

It definitely matters to the translation process though, because there are
lots of duplicate declarations which are guarded by #if checks. Since
fbfrog does preprocessing but does not necessarily complain about
incomplete input, it's best to include windows.h first everytime, because
that's the main entry point. Then at least we can be sure that from
windows.bi's point of view everything will work.

Of course that doesn't work with all headers; e.g. ntdef.h isn't supposed
to be used together with windows.h, or winsock2.h which is supposed to be
#included before windows.h, so it can override winsock.h...
winapi: Preserve WIN32_LEAN_AND_MEAN in windows.h
winapi: Move options into winapi.fbfrog
winapi: #include sspi.h again when translating ntsecpkg.h
winapi: Handle winsock/winsock2/mswsock
winapi: Don't expand #defines which conflict with field/param names
winapi: Add more documentation
raw: Regenerate with latest fbfrog
winapi: Don't rename fields conflicting with global #defines

To match the C headers, the fields now have their original names.
The global #defines of the same name may change the identifiers, at least
if seen first.

When this happens, it will probably go unnoticed and not cause any
problems, as long as it affects both the declaration and any access to
the field.

Renaming the fields epxlicitly would require further fix ups in macros
containing accesses to these fields (because fbfrog doesn't update
identifiers in field accesses currently).
winapi: Support a few selected _WIN32_WINNT values

Ideally all would be supported, but
a) fbfrog's #if block generation isn't pretty enough for that yet
b) with the way the translation is done currently it's just too slow to
   do more
winapi: objidlbase