Request intent status (in model to-be / not in model to-be)

[turnerrainer]

AS A Trainer I WANT TO know if the intent would be used if a new model was to be trained now SO THAT I CAN see which intent will be usable for End Users

Temporary list of API endpoints

Acceptance Criteria

• [x] If intent is as (.yml) file, it must be mapped to domain.yml file intent list
• [x] If intent is not in the model (.tmp file), intent is not mapped in the domain.yml file intent list

DSL

• [x] GET endpoint /intents/in-model
• [x] List all intents listed in domain.yml under the section intents

[RaulAltmae]

Pull request https://github.com/buerokratt/Training-Module/pull/184

[KasparMinn]

PR: https://github.com/buerokratt/Training-Module/pull/284

This pull request creates the base functionality for, importantly, not only seeing whether or not an intent's status was in model, but also adding or removing it from the model if necessary. This functionality did not exist before in both an incomplete front-end as well as no appropriate DSLs for it on the back-end. Currently adding and removing an intent from the model only includes adding it to the Domain file, but adding new things is now made easy.

• Added a separate DSL that handles adding/removing the intent from model.
• Added add/remove intent to or from model functionality to the front-end button.