Webd and elektrad bulk kdb meta-set

[tmakar]

Basics

• Short descriptions of your changes are in the release notes
  (added as entry in doc/news/_preparation_next_release.md which contains _(my name)_)
  Please always add them to the release notes.
• Details of what you changed are in commit messages
  (first line should have module: short statement syntax)
• References to issues, e.g. close #X, are in the commit messages.
• The buildservers are happy. If not, fix in this order:
  • add a line in doc/news/_preparation_next_release.md
  • reformat the code with scripts/dev/reformat-all
  • make all unit tests pass
  • fix all memleaks
  • fix the CI itself (or rebase if already fixed)
• The PR is rebased with current master.

Checklist

• I added unit tests for my code
• I fully described what my PR does in the documentation
  (not in the PR description)
• I fixed all affected documentation (see Documentation Guidelines)
• I fixed all affected decisions (see Decision Process)
• I added code comments, logging, and assertions as appropriate (see Coding Guidelines)
• I updated all meta data (e.g. README.md of plugins and METADATA.ini)
• I mentioned every code not directly written by me in reuse syntax

Review

• Documentation is introductory, concise, good to read and describes everything what the PR does
• Examples are well chosen and understandable
• Code is conforming to our Coding Guidelines
• APIs are conforming to our Design Guidelines
• Code is consistent to our Design Decisions

Labels

• Add the "work in progress" label if you do not want the PR to be reviewed yet.
• Add the "ready to merge" label if everything is done and no further pushes are planned by you.

[tmakar]

This PR introduces:

• Implement bulk meta key creation request (the new request supports to add multiple meta keys to a key in one request)
• Add shell recorder test in README for this new implementation
• Fix existing shell-recorder test to use correct key name

NOTE: Implementation is done for elektrad (GO) and for webd (NodeJS) .

[atmaxinger]

For me this looks okay from a pure idea standpoint. However, I can't review the code, as I've never seen a single line of Go code in my life.

It's also a bit off-putting that there are no tests, but apparently, there are no existing tests for elektrad or webd either.

[tmakar]

It's also a bit off-putting that there are no tests, but apparently, there are no existing tests for elektrad or webd either.

Yes, I noticed this as well.

I now thought that it is better to put at least a shell-recorder test into the README than no test at all.

I will may in the next iterations work on adding tests, at least for the elektrad tool.

[tmakar]

@atmaxinger There actually are tests for elektrad but not for webd. I was wrong. meta_handler_test.go

[atmaxinger]

please rebase to resolve merge conflict

[atmaxinger]

jenkins build libelektra please

[markus2330]

LGTM