Cmsplugin-blocks

--------------------------

* Dropped support for Python 3.8;
* Dropped support for Django 3.2;
* Added support DjangoCMS>=4.1 (DjangoCMS 4.0 has never been released);
* Package does not install ``djangocms-text-ckeditor`` anymore but still supports it
for now;
* Added support for ``djangocms-text`` that is the futur of CMS text editor;
* Make rich editor optional, if none is installed then the plugin still works but use
the builtin Textarea widget;

--------------------------

* Added new optional field ``link_name`` to Card model;

--------------------------

* Introduced a new setting ``BLOCKS_FEATURE_ALLOW_MULTIPLE_CLASSES``:

* When true it allows whitespace in Feature value so it can contains multiple CSS
classnames divided by a whitespace like ``cell col-md-12 red``;
* When false the whitespaces in Feature value are considered invalid;
* On default this settings is false so whitespaces in value are considered invalid;
* Uniqueness is now enforced on scopes values from property ``scoped_features``;
* Importation correctly validate this behavior so you won't be able to import
Features including whitespaces if the setting does not allow it;
* Exportation does not care about this behavior and will indifferently dump Feature
values whether they include whitespace or not;

* Fixed Accordion template in sandbox;
* Added more explicit error messages for invalid items in Feature import form;
* Made some minor improvements on Feature admin;
* Updated PO and MO files for last Feature changes;
* Enabled "todo" extension module in documentation;

--------------------------

* Fixed migrations 0008, 0009, 0011 and 0012 that were still using harcoded choices.
This was an issue for projects that were changing value of settings
``BLOCKS_ACCORDION_TEMPLATES`` and ``BLOCKS_FEATURE_PLUGINS``, Django would detect
pending useless migrations from this package.

This is safe to upgrade except if you blindly followed the Django warning and created
then applied these pending automatic migrations, which you should never do. If so, you
will have to remove these created migrations from your package installation and clean
your migration history.
* Updated script to freeze local dependencies;
* Finally removed Django version restriction and added support for Django 5.1 since
DjangoCMS won't officially support it but it still basically works;
* Added minimal requirement versions to help Pip resolving;

--------------------------

Removed SmartMedia purge signals from every model since it is not compatible with
DjangoCMS plugin system and caused erratic issues of lost media files. **You will
have to manage purge yourself if neeeded**.

--------------------------

* Added new plugin *Accordion*;
* Disabled annoying Carousel autoplay in Slider template for sandbox;
* Relaxed versions for requirements ``furo`` and ``sphinx-copybutton``;
* Restricted Django requirement version to ``<5.1``, since DjangoCMS 3 is not
compatible with Django>=5.1 and for now this application is not yet planned to
support DjangoCMS 4;