UnexpecTEDIntentPolicy final merge

[dakshvar22]

Proposed changes:

This PR introduces a new policy called UnexpecTEDIntentPolicy and accompanying functionality for different rasa commands like rasa train, rasa test, etc.

Note: The whole feature development was broken down into smaller PRs which were independently reviewed. No code was directly committed to this branch without being peer reviewed as part of a PR.

To get a better understanding of the feature implementation, please head over to the implementation document.

All the smaller PRs are listed below -

Completed PRs

Research:

• Implement a new tracker featurizer IntentMaxHistoryTrackerFeaturizer
• Implement a new loss function MultiLabelDotProductLoss
• Implement the policy IntentTEDPolicy
• Add a tolerance parameter to policy
• Add severity to policy's output metadata and make use of ranking_length
• Fix logic to ensure predictions are skipped when needed.
• Experimental label and more integration tests
• Docs for feature (changelog, migration guide will be part of this)

Engineering:

• Add a new default action_unlikely_intent action
• Add IntentTEDPolicy to default configuration
• Adapt rasa interactive
• Support for rasa test IntentTEDPolicy: rasa test updates #8843 and IntentTEDPolicy: Updated rasa test tests #8949
• Update rasa data validate to warn if action_unlikely_intent is present in story training data.
• Sort warnings from rasa test by severity

Note: The introduction of a new default action will make the overall release breaking backwards compatibility of models.
This has been communicated in the changelog and migration guide

Status (please check what you already did):

• added some tests for the functionality
• updated the documentation
• updated the changelog (please check changelog for instructions)
• reformat files using black (please check Readme for instructions)

[HotThoughts]

Gitleaks still complains about the commits that push secrets to rasa/data/test_moodbot/credentials.yml . Is it intentional to keep those secrets in the code? If yes, one thing that we can do is to tell gitleaks ignore this file.

[wochinge]

@HotThoughts it's just a fake config and no real credentials

[HotThoughts]

Fix here 😊. The gitleaks should pass now.

• ignore fake credentials #9108

Update: Oh no. Gitleaks still complains about it. Let me check.