Incorrect sling:basename added to the new language

[painttred]

Steps to reproduce:

1. Create a new dictionary with a custom basename (e.g. test-basename)
2. Select the newly created dictionary and add a new language to it

Actual result:
The newly created language contains sling:basename set as a path to the dictionary rather than the basename that was provided initially.

Expected result:
The newly created language should contain the same basename as it was set initially during dictionary creation.

Technical details:
I see that there is a basename item that exists in the language creation component https://github.com/orbinson/aem-dictionary-translator/blob/main/ui.apps/src/main/content/jcr_root/apps/aem-dictionary-translator/content/granite/dialog/dictionary/language/create/.content.xml#L40 . However, it looks like it does not have any resource mapped to it. Because of that, basename is empty here https://github.com/orbinson/aem-dictionary-translator/blob/main/core/src/main/java/be/orbinson/aem/dictionarytranslator/services/impl/DictionaryServiceImpl.java#L118 and as a result, the path to the dictionary is set as a basename instead.

[kwin]

Base Names can be set independently for each dictionary (=messages for one languages), therefore I am not sure there should be any fallback. Which value to use in case the dictionaries below a common parent don't share base names. Which base name to use then for a new dictionary? All in all I would say that it is fair to require the base name to be set for each dictionary/language individually.

[kwin]

See also #216