feat: translation flows, revision conflicts, delete scopes, article moves and a target site for new articles

features/article_translation_create.feature

@@ -147,7 +147,7 @@ Feature: Create a translation of an article version
     And the result, errors, headers and stored data are exactly those of POST /v1/article/10/translations with the same lang, title and source
     And the same use case runs for both
 
-  Scenario Outline: POST /v1/article/ is unchanged when it is not a translation
+  Scenario Outline: POST /v1/article/ is unchanged when it is not a translation (it creates in the default site when no site is given; a "site" key names the target site, see localization_translation_flows)
     Given a valid jwt cookie for a writer
     When the client sends POST /v1/article/ with <body>
     Then the response status is <status>
@@ -162,6 +162,8 @@ Feature: Create a translation of an article version
       | {"title":"Neuf","story_id":5}         | 400    | the body is apperr.BodyErrorMessage                          |
       | {"title":"Neuf","lang":"fr","story_id":999} | 404 | the body is "Article not found"                          |
       | {"title":"Neuf","copy":true}          | 400    | the body is apperr.BodyErrorMessage                          |
+      | {"title":"Neuf","lang":"fr","story_id":5,"site":"atelier"} | 400 | the body is apperr.BodyErrorMessage (a site with a translation is refused) |
+      | {"title":"Neuf","lang":"fr","site":"atelier"} | 201 | a new story is created in fr on site atelier |
 
   Scenario: PATCH still ignores lang, story_id and source fields
     Given a valid jwt cookie for a writer