SKALED-1900 release build with separate debug info

[dimalit]

1. All dependencies, are built with -O3 and without -g.
2. skaled is built with -O3 but WITH -g.
3. -rdynamic removed.
4. skaled binary is stripped, but it's copy wit debug info is kept.

CUSTOM BUILD Now contains option to build maximally optimized "Release" configuration

Consequences:

1. Stack trace printed by skaled on crash will not contain any function names.
2. gdb will be able to use skaled-debug file to load debug info for original skaled
3. addr2line will be able to convert addresses from skaled's printed stack trace into source code locations using skaled-debug binary

Testing:
1

objdump -h skaled | grep debug
nm -a skaled

2 Execute strip command on skaled and see that it's size didn't change
3 ojdump -h <file> | grep debug on all project libraries shows no result too.

skaled binary size 29575576

[github-actions]

SUGGESTIONS BEFORE MERGE:

1. Build custom container here: https://github.com/skalenetwork/skaled/actions?query=workflow%3A%22Custom+Docker+and+Binary%22
2. Test it here: https://github.com/skalenetwork/skale-ci-integration_tests/actions?query=workflow%3A%22Skaled+Nightly+Tests%22
3. Edit VERSION file appropriately to your changes!
   See https://skalelabs.atlassian.net/wiki/spaces/SKALE/pages/2444951553/Branching+instructions

[olehnikolaiev]

maybe we can add this library to our deps script instead of installing in through apt-get? seems like it is pretty easy to install https://github.com/lz4/lz4