Move template configuration to source-mappings.json

[premun]

Context

During VMR synchronization, we create the third party notices file based on the contents of the VMR.
It is created from templates stored in the SDK repo.
The location of these templates is hardcoded right now but we should probably have these configurable from source-mappings.json. Once we move to the full flat flow, the template will move somewhere else in the VMR so it will be easier to make the move together with the change in source-mappings.json.

Goal

Add settings for component list and third party notices templates to source-mappings.json and use those settings when we are generating these files.