Making localization sync

[Ahmedmhmud]

For #216,Localization.forLocale can be synchronous if we get rid of the async reading and this PR solves the problem of relying on ftl files by removing them entirely and replacing them with JS module that has the same content and can be imported and by relying on JS module, we can safely switching Localization.forLocale to synchronous

[jdesrosiers]

Let's make it one file per locale like it was, just make it .js instead of .ftl. Then translations.js should import each locale file to construct the map.

[jdesrosiers]

You can't put text fixtures here because it will be usable outside of tests as well.

[jdesrosiers]

This is still a problem. You need to handle test fixtures in a way that doesn't make them available to users.

[Ahmedmhmud]

Hi @jdesrosiers , I did isolate locales and construct the map in translations.js

[Ahmedmhmud]

Now, It is abstracted as before but using the map to avoid file operations that requires async pipeline
I deleted the fx-TR file to prevent exposing tesing details and imported translations map to apply runtime operations for testing using beforeAll & afterAll