fix(core): pass application config to nest container when using application context

[SocketSomeone]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

Issue Number: #12165 #9017

NestContainer init w/o application config.
NestFactory.initialize take default value for application config. For that reason we got application config undefined and no global enhancers.

What is the new behavior?

After bootstrap application allow to create fns via ExternalContextCreator with global enhancers. For that we need to pass ApplicationConfig to container.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 4338e9e0-055e-4201-9c62-52c00ec2f1d4

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 92.813%

---

Totals
Change from base Build de330e86-7c2b-484a-b17f-f872998b5610:	0.0%
Covered Lines:	6392
Relevant Lines:	6887

---

💛 - Coveralls

[kamilmysliwiec]

LGTM