Introduce possibility of mandatory non-deletable key values

[solita-sabinaf]

Summary

We would like to have some keys in key values that are already present in UI so that user doesn't need to type them, and that cannot be deleted

Unit tests

Tested with and without mandatory keys specified in the bootstrap.json

Use this to test:

"mandatoryKeyValuesSet": {
    "stopPlace": {
      "rail": ["uicCode", "ersad.PRMTSICompliantStation", "ersad.AccessibleStation"],
      "bus": ["service_level"]
    },
    "quay": {
      "all": ["digiroad_rubbish_disposal_equipment"],
      "tram": ["digiroad_id"],
      "bus": ["digiroad_id"]
    }
  }

[solita-sabinaf]

The diff looked better on a commit level :/

[testower]

That's ok, the benefit is now the file history can be tracked across the rename.

[sfatali]

Ping @a-limyr, this is ready for review

[a-limyr]

Looks good, found two minor things. Good job!

[a-limyr]

Probably an old bug, but this line will result in always showing the edit, delete and create new buttons even when not logged in.

[solita-sabinaf]

Thank you, that's a great catch! That was something I added and forgot to clear away. Along the way removed the const keyValuesOrigin as it wasn't used anywhere

[a-limyr]

For new keyValues there is run two dispatches, one for create and then on for update. I would suggest adding a return statement after create to avoid that.

[solita-sabinaf]

Good point 👍