[Request] Add a factory binding type which gives access to a subset of the container interface

[mscharley]

Is your feature request related to a problem? Please describe it.

Some bindings need access to the container, eg. a binding to create a child container. Currently you could bind in a function to generate child containers but it would need access to the original container somehow which leads to constructs like container modules which take the container in as an argument instead of being agnostic.

Describe the solution you'd like.

Ideally this factory binding would leverage the existing toDynamicValue logic to provide the planner a way to know ahead of time what dependencies the factory has.

Example client-side usage:

const requestContainerFactory = new Token<(req: Request) => interfaces.Container>();

bind(requestContainerFactory).inSingletonContext().toFactory(
  [dependencyToken1, dependencyToken2],
  ({ container }) => (dep1, dep2) => (req) => {
    const reqContainer = container.child();
    // ... bind modules necessary for your requests.
  },
);

Describe alternatives you've considered.

No response

Any additional context you'd like to provide?

No response

[mscharley]

Implemented in #88