feat(template-controller): ability to have a container per factory

[bigopon]

📖 Description

Currently template controllers reuse the container from their owning renderer (custom element), as an optimization, also a requirement since they need to retrieve the resources information from there. This works well for all built in template controllers as they don't need to do anything special with their view factories.
Though, for application custom controller, sometimes it's more desirable to have separate container for dynamic DI work.

This PR adds a new option containerStrategy for custom attribute definition to enable this. The acceptable values are reuse and new, and the default is reuse, which is the existing behavior.

🎫 Issues

Resolves #1923

Thanks @mxjp

[codecov]

Codecov Report

Attention: Patch coverage is 90.00000% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 88.56%. Comparing base (32f00ed) to head (cce8439).
Report is 5 commits behind head on master.

Files	Patch %	Lines
packages/kernel/src/di.ts	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1924      +/-   ##
==========================================
+ Coverage   88.47%   88.56%   +0.08%     
==========================================
  Files         260      262       +2     
  Lines       22843    22876      +33     
  Branches     5258     5283      +25     
==========================================
+ Hits        20211    20260      +49     
+ Misses       2632     2616      -16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Sayan751]

Thanks @bigopon! Can you please add a test case of nesting?

<div example.bind="1">
  <my-ce /><!-- value of injected IExample is 1 in my-ce -->
  <div example.bind="2">
   <!-- value of injected IExample is 2 in my-ces -->
    <my-ce />
    <my-ce />
  </div>
  <my-ce /><!-- value of injected IExample is 1 in my-ce -->
</div>