[ide extension api] add namespace api to ease extraction

[NilsJacobsen]

Problem

Translations are automatically prefixed with a namespace (i18next + next-intl) that works great, but when i extract a new string the namespace does not automatically added so the translation will end up in the wrong place. When I try to fix it by adding the namespace manually during extraction it gets placed correctly, but now we have a double prefix.

Possible Solution

• Add namespace API to custom app API of ide extension. We parse it anyway we just need to expose it. Then the ide extension can just add it to the extraction.

Pro: Easy support for namespaces extraction
Cons: We bring more opinionated namespaces into the game that are handled differently by libraries.

Possible fix for cons

• Take opinionation out of the game by just naming it id prefix. Weather it is a namespace a key prefix or something else can be handled by the plugin.

Curious what you think guys. @felixhaeberle

[felixhaeberle]

Sounds reasonable, let's wait until more people have this requirement.

@NilsJacobsen Also, which data do you need at what point of time – can you outline an API?