Add property to support the restriction for the Steps length in the report

#### I'm submitting a ...
- [x] feature request

Add a property to support the restriction for the Steps length in the report, for example,
`allure.max.title.length' as was in Allure 1.

#### What is the current behavior?
Property `allure.max.title.length` is ignored.

#### What is the expected behavior?
When `allure.max.title.length=1000` is added in `allure.property` file, the logged steps in the Allure report should be cut after 1000 symbols.

#### What is the motivation / use case for changing the behavior?
Sometimes, very big values are passed to methods annotated with @Step annotation, and there is no obvious way to restrict the number of characters to be printed in the report.
For example, if 'allure-assertj' is used, and the JSON objects to be compared are large, there is no way to restrict how they are displayed in the report.
On the following sample screenshot there are more than 2000 characters:
and this is just about 1/3 of the whole JSON object. And all its characters are displayed in the step.

#### Additional information
The issue was discussed here https://github.com/allure-framework/allure2/issues/1150

| Allure version | 2.13.5 |
| --- | --- |
| Test framework | testng@6.9.10 |
| Allure integration | allure-testng@2.13.5 |
| Generate report using | allure-maven@2.9 |

Commencez par déterminer comment la propriété allure.max.title.length et les valeurs de @Step sont gérées lors de la génération des étapes du rapport. Implémentez la limite demandée afin que le texte de l’étape journalisée soit tronqué au nombre de caractères configuré, puis vérifiez qu’une valeur telle que 1000 modifie la sortie du rapport généré.

Rédigé par le modèle d'indexation à partir du texte de l'issue.