Ask users to create redirects in the node delete process

Editors are prompted to create a redirect on node delete.

Ready to review.

Additional checks have been added to ensure that the function _redirect_delete_helper__set_key_value_data() receives the correct values. There was a case where an error was generated due to passing a NULL value when a node search was performed to create the redirect, but the node was subsequently deleted, leaving the field empty.

A new setting will be added to decide if the redirection to another node will be mandatory. Depending on the use case, the form will be displayed in one way or another.

A new tab has been added in the Redirect module configuration to allow defining, using a checkbox, whether the redirection of nodes when deleting them should be mandatory or not. The form will continue to be modified to adapt the behavior to this configuration.

The logic has been completed so that the redirection field is mandatory when deleting a node, in case the corresponding option is enabled in the module configuration. In this way, the behavior of the form is dynamically adjusted as defined by the administrator.

Hello Antonio:

Just I did some small changes:
- Added settings schema and default value.
- If the redirect is required, we don't need to show the checkbox.

It works as expected.

Thank you very much.

It would be great if a message were displayed when a node is deleted and a redirection occurs. Currently, the user is only informed that the node was deleted, but not that they have been redirected.

The functionality to enforce redirection is excellent; however, it currently applies to all content types. In some cases, certain content types are not used as full pages but rather as components. Therefore, it would be helpful to configure when this functionality should be applied.
To address this, I propose adding a form that allows us to select the applicable content types.