Avoid usage of localized strings before initialization during import in many modules

This happens if import is done before i18n setup
(InstallLocalRessources()).
This affects PLCOpenEditor mostly. Beremiz IDE is free from this issue, but moving
initialization from import should make modules more robust.
Otherwise execution result depends on where and when import was done
and this is not a good thing.

Some modules (ConfigTreeNode, features, CodeFileEditor related
classes) still have this, but they are used only in Beremiz.
Most problems result in non-working internatialization.
In some cases (VariablePanel) there is backtrace, because localized
key is not found in non-localized dictionary.

     1

#Encoding of BACnet Object Types;;;

     2

#Code;Object Type;;

     3

0;Analog Input;;

     4

1;Analog Output;;

     5

2;Analog Value;;

     6

3;Binary Input ;;

     7

4;Binary Output;;

     8

5;Binary Value;;

     9

6;Calendar;;

    10

7;Command;;

    11

8;Device;;

    12

9;Event-Enrollment;;

    13

10;File;;

    14

11;Group;;

    15

12;Loop;;

    16

13;Multistate Input;;

    17

14;Multistate Output

    18

15;Notification Class

    19

16;Program

    20

17;Schedule

    21

18;Averaging

    22

19;Multistate Value

    23

20;Trend Log

    24

21;Life Safety Point

    25

22;Life Safety Zone

    26

23;Accumulator

    27

24;Pulse Converter