Update Envoy to 38c5c86 (Mar 25, 2024)

[eric846]

• .bazelrc updated from upstream
• tools/code_format/config.yaml updated from upstream
• In an incredibly confusing refactor:
  • Envoy's FaultFilterConfig started taking a CommonFactoryContext instead of a Runtime and TimeSource.
    • Updated HttpDynamicDelayDecoderFilterConfig to store a CommonFactoryContext& instead of a TimeSource&, so that it has a CommonFactoryContext& to use when constructing a FaultFilterConfig.
      • How to get a CommonFactoryContext when creating the HttpDynamicDelayDecoderFilterConfig? HttpDynamicDelayDecoderFilterConfigFactory has access to a Envoy::Server::Configuration::FactoryContext, which has a serverFactoryContext() method. ServerFactoryContext is a subclass of CommonFactoryContext.
  • Envoy has started calling serverFactoryContext() on the NighthawkServerInstance, which had a PANIC placeholder there. This was discovered in the integration tests.
    • Gave NighthawkServerInstance a reference to a NighthawkServerFactoryContext to return in serverFactoryContext(), replacing the PANIC placeholder.
    • In order to remove a circular dependency, took away NighthawkServerFactoryContext's reference to a NighthawkServerInstance, to which it delegated many calls. Now NighthawkServerFactoryContext stores its own references to the underlying objects formerly wrapped in the NighthawkServerInstance.
  • I originally assumed the above two things were related, but it appears that both arose here by coincidence.