[#1316] Add title-description to banner plugin

[vaszig]

Discussed with Alex as well, this does not make sense to be combined in one plugin. We need the title and description to be available in another section (in the main-grid and not in the banner), so a second plugin was created for this purpose.

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (develop@f6fe153). Click here to learn what that means.
The diff coverage is 97.14%.

@@            Coverage Diff             @@
##             develop     #610   +/-   ##
==========================================
  Coverage           ?   96.41%           
==========================================
  Files              ?      579           
  Lines              ?    19951           
  Branches           ?        0           
==========================================
  Hits               ?    19235           
  Misses             ?      716           
  Partials           ?        0           

Impacted Files	Coverage Δ
src/open_inwoner/conf/base.py	95.37% <ø> (ø)
src/open_inwoner/cms/banner/models.py	86.66% <85.71%> (ø)
src/open_inwoner/cms/banner/cms_plugins.py	100.00% <100.00%> (ø)
src/open_inwoner/cms/banner/forms.py	68.75% <100.00%> (ø)
...r/cms/banner/migrations/0003_auto_20230511_1125.py	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Bartvaderkin]

Why do we need a name-field if we're not showing it?

[vaszig]

I was thinking that we do not have any required fields, so maybe I should remove name and make image a required field?

[vaszig]

Discussed with Bart, name fields are not useful. Image and title will be the required fields for the two models (BannerImage and BannerText).

[alextreme]

Reasoning why I didn't request to remove 'name' is that I often see plugins with an (internal) name which is only used for plugin.str , this to make the name visible in the CMS when editting the page.

This is mostly used for CMS pages with long lists of plugins, so I agree that the benefit for only the bannerplugin is quite limited.

[jiromaykin]

So this text area is really only visible when logged in? Becasue when you're logged out, there is a different 'welkom' area visible that is still there and cannot be removed by the user and is configarable from the Admin.

So when am logged out i still see the 'Koptekst homepage' area on Home because that is a required field - i am not sure if that one needs to be required and visible still - what do you think @alextreme ?

[alextreme]

So this text area is really only visible when logged in? Becasue when you're logged out, there is a different 'welkom' area visible that is still there and cannot be removed by the user and is configarable from the Admin.

So when am logged out i still see the 'Koptekst homepage' area on Home because that is a required field - i am not sure if that one needs to be required and visible still - what do you think @alextreme ?

This was discussed with @vaszig as a workable intermediate solution (populating the anonymous page via the Algemene Configuratie, and the logged-in homepage via the CMS). But I agree it isn't ideal, I would like to have the anonymous homepage configurable via the CMS too but that would be a next step.

[Bartvaderkin]

Last week I started adding tests for the plugins, for example (some others as well):

https://github.com/maykinmedia/open-inwoner/blob/develop/src/open_inwoner/cms/products/tests/test_plugin_product_location.py

We should do that for all plugins.