Fix issues when building more Quiche tests for iOS and Windows

Addresses additional build and test failures for tests run as part of net_unittests in Chromium for iOS and Windows.

Calling WSAStartup in the connect tests avoids the following error in multiple tests on the win-rel bot:
```
ERROR:quic_name_lookup.cc(36)] Failed to look up localhost: Either the application has not called WSAStartup, or WSAStartup failed.
```

Using QUICHE_NO_EXPORT avoids errors like the following on win_chromium_compile_dbg_ng:
```
lld-link: error: undefined symbol: __declspec(dllimport) public: class absl::Status __thiscall quiche::BTreeScheduler<int, int>::Register(int, int const &)
```

The CustomStructWritesTooLittle test changes avoids an unused variable error on ios-simulator.

PiperOrigin-RevId: 607146214
6 files changed
tree: dc47efdbd3418538ae06f090dbfd3d864c9b12b1
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. .bazelversion
  6. BUILD.bazel
  7. CONTRIBUTING.md
  8. LICENSE
  9. README.md
  10. WHITESPACE
  11. WORKSPACE.bazel
README.md

QUICHE

QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.

There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:

To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:

To contribute to QUICHE, follow instructions at CONTRIBUTING.md.

QUICHE is only supported on little-endian platforms.