Update water park docs to match current release about fluidframework HOT 2 CLOSED

Hello, I'm not sure if this is the right place to ask this question, but I'm trying out the waterpark and I am only able to load a subset of components:

Expected: ability to load any component listed on Verdaccio. For example, I might try to load @fluid-example/[email protected], but I get this error:

Error: UrlRegistry: https://pragueauspkn-3873244262.azureedge.net/@fluid-example/[email protected]: instantiateComponent does not exist on entrypoint

from fluidframework.

@danmarshall Thanks for the info! This is expected at the moment. The short story is that we don't currently have a mechanism to identify compatibility between a runtime version used by the hosting container - which is the water park in this case - and components. In other words, there's no way for the water park to filter the list of components it knows about based to only load versions that are compatible with the runtime that it uses. This is on our radar. I couldn't find the issue tracking it though so I filed #835.

from fluidframework.