Config validation for ECA models

Problem/Motivation

Let's build the schema and everything else that's required to be able to validate ECA config entities.

Note: this is related to 📌 Reconsider the structure of separated eca config entities Active in terms of the proprietary data should not be validated, regardless where this will eventually be stored.