Hooks / components for data from other agencies

@adamscarberry @jbkolze
I think it makes sense for us to build hooks/components for this kind of data, if we don't do it so others follow our lead, then they will just do it themselves in haphazard ways. This comes with a couple considerations though:

1. We need to come up with some disclaimer text that can be used by a consumer of the data/component.
2. We could add a component that is an orange <TiInfo /> or other icon that pops up the disclaimer when clicked.
3. We require that when using the hook/display component you must use the disclaimer text or disclaimer component.
4. I wouldn't try and programmatically enforce this, but the note in the docs should say that we reserve the right to break their sites if they don't follow our usage guidelines.

Originally posted by @willbreitkreutz in https://github.com/USACE/groundwork/issues/49#issuecomment-2093326612

This issue to track a path forward on this conversation.

Start by reading the discussion referenced from issue #49 and the two comments on this issue, since no implementation files or tests are identified. Define the agreed scope for hooks/components, disclaimer text, the info-icon component, and usage documentation before implementation can be considered complete.