Database design for one key with multiple values
Instead of the dynamic number of columns (1 for each new language), I expect it would easier to manage this in the form of two related tables: 1. with your key and potentially one or more properties (to which new rows can be added for each new word) and 2. a table with translations for each key in table 1.

I have recently reviewed some strategies on this and found the below linked answer to be most useful, which expands on what I note above.

The answer provided a sample table:

    CREATE TABLE T_PRODUCT (pr_id int, PRICE NUMBER(18, 2))
    CREATE TABLE T_PRODUCT_tr (pr_id INT FK, languagecode varchar, pr_name text, pr_descr text)


https://stackoverflow.com/a/323365/10340388