Rasa

- [10471](https://github.com/rasahq/rasa/issues/10471): Fix load method of LexicalSyntacticFeaturizer to make the class inheritable.
- [7645](https://github.com/rasahq/rasa/issues/7645): Do not print warning when subintent actions have response.

- [10413](https://github.com/rasahq/rasa/issues/10413): The value of the `RASA_ENVIRONMENT` environmental variable is sent as a header in messages logged by `KafkaEventBroker`.
This value was previously only made available by `PikaEventConsumer`.

Bugfixes
- [10458](https://github.com/rasahq/rasa/issues/10458): Make `action_metadata` json serializable and make it available on the tracker. This is a backport of a fix in 3.0.0.

- [10381](https://github.com/rasahq/rasa/issues/10381): [#10381](https://github.com/RasaHQ/rasa/issues/10381): Validate regular
expressions in nlu training data configuration.

- [10241](https://github.com/rasahq/rasa/issues/10241): [#10241](https://github.com/RasaHQ/rasa/issues/10241): Bump TensorFlow version to 2.6.2.
- [10257](https://github.com/rasahq/rasa/issues/10257): [#10257](https://github.com/RasaHQ/rasa/issues/10257): Downgrade google-auth to <2.

- [9949](https://github.com/rasahq/rasa/issues/9949): Fixed new intent creation in `rasa interactive` command. Previously, this failed with 500
from the server due to `UnexpecTEDIntentPolicy` trying to predict with the new intent not in
domain.
- [9982](https://github.com/rasahq/rasa/issues/9982): Install mitie library when preparing test runs. This step was missing before
and tests were thus failing as we have many tests which rely on mitie library.
Previously, `make install-full` was required.

Miscellaneous internal changes
- [10146](https://github.com/rasahq/rasa/issues/10146), [#9989](https://github.com/rasahq/rasa/issues/9989)

- [9771](https://github.com/rasahq/rasa/issues/9771): Fixed a bug where `rasa test --fail-on-prediction-errors` would raise a
`WrongPredictionException` for entities which were actually predicted correctly.

This happened in two ways:
1. if for a user message some entities were extracted multiple times (by multiple entity
extractors) but listed only once in the test story,
2. if the order in which entities from a message were extracted didn't match the order
in which they were listed in the test story.

Improved Documentation
- [9691](https://github.com/rasahq/rasa/issues/9691): Improve the documentation for training `TEDPolicy` with data augmentation.