[feat] add support for JSON imports

[derkoe]

With this change you can use JSON as the source for your translation texts. See #151

Then plain JSON can be used to store the texts (with en as the base language):

src/i18n/en/index.ts:

import * as en from './texts.json';
export default en;

src/i18n/en/texts.json:

{
    "HI": "Hello {name}!",
    "BYE": "Bye bye"
}

src/i18n/de/index.ts:

import type { Translation } from '../i18n-types'
import * as deJson from './texts.json'
const de: Translation = deJson;
export default de

src/i18n/en/texts.json:

{
    "HI": "Hallo {name}!",
    "BYE": "Auf Wiedersehen"
}

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time.
• Prefix your PR title with [feat], [fix], [chore], or [docs].
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm run test and lint the project with pnpm run lint

[ivanhofer]

Thanks for this PR.
Could you please also update CHANGELOG.md?
It will be a minorversion bumb 😉

[bitdom8]

Thanks @derkoe

[whalemare]

This is worked only as json importing and not for a translations type checking, right?
Types inside not base json files always be "string", because of typescript limitations

[ivanhofer]

yes, this is a limitation on how TypeScripts type system parses the json file

[bitdom8]

Thanks