Root request scope

[tonyhallett]

Description

Added a new binding scope - inRootRequestScope()
This works similarly to request scope but applies to all container.get calls that occur during the 'root' container.get. This allows scope to be shared across toDynamicValue

container.bind<Weapon>(TYPE.DynamicWeapon).toDynamicValue((context) => {
    return context.container.get<Weapon>(TYPE.Weapon);
});

This is facilitated by Context.parentContext, which is managed by Container._planAndResolve, and Context.rootRequestScope which is managed by the resolver.

Related Issue

#1143

Motivation and Context

As soon as you use toDynamicValue you cannot resolve a previously resolved value unless it is singleton scoped. With this code change there is now the concept of a root request which can be scoped to.

How Has This Been Tested?

TDD. Test that demonstrates what cannot be achieved with request scope that can now be achieved with root request scope.

Types of changes

• Updated docs / Refactor code / Added a tests case (non-breaking change)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated the changelog.

As always, if you merge these changes I will happily update the documentation.

[tonyhallett]

Parent context should be a stack. I have a better abstraction that uses the ideas in this pull request that will add in a fresh pull request shortly.