COM-957: Add basic warning entity

[raphaelblum]

---

Description:
In the Warning Module there should be a warning entity where warnings are saved.
Entries into this table should later be added with a validator or via a block, maybe even manually.
This is the start of the central warning system in order to have a basic table and to be able to start with the validator afterwards.

Questions:

• Move warning.entity and related code to cms-api. For now I think it makes sense to keep it in the demo, since I easily can rerun api generator again. Or should I look into making the api generator available also in the cms-api package? I'm not sure if this can or should work.
• Changeset: I think it makes sense adding a changeset for the Feature branch instead of a lot small changesets while developing in the feature branch, or what do you say?

My next Step:
Detecting warnings for a simple example, maybe for a Job or for invalid Blockdata. Finding the "error" and creating a warning.

Later on we probably need something like a Message or Warning Info. I'd look into this later. I haven't thought about how this could work yet (intl in api?)

PR Checklist

• Verify if the change requires a changeset. See CONTRIBUTING.md
• Link to the respective task if one exists:
• Provide screenshots/screencasts if the change contains visual changes

Screen.Recording.2024-10-04.at.10.58.36.mov

[johnnyomair]

@raphaelblum do you want us to review this, or is it WIP?

[raphaelblum]

@raphaelblum do you want us to review this, or is it WIP?

still Draft, unfortunately, but it seems like I'm having time to continue working on it now

[johnnyomair]

Move warning.entity and related code to cms-api. For now I think it makes sense to keep it in the demo, since I easily can rerun api generator again. Or should I look into making the api generator available also in the cms-api package? I'm not sure if this can or should work.

Yes, keep it in the Demo for now.

Changeset: I think it makes sense adding a changeset for the Feature branch instead of a lot small changesets while developing in the feature branch, or what do you say?

Yes, one changeset for the feature (and preferably docs as well).