Add milestone numbers to images in user/project

Give these images milestone numbers so we can tell how old they are.

doc/user/project/canary_deployments.md

@@ -96,7 +96,7 @@ quick and clear insight into the status of each environment and deployment.
 Canary deployments are marked with a yellow dot in the deploy board so that you
 can quickly notice them.
 
-![Canary deployments on deploy board](img/deploy_boards_canary_deployments.png)
+![Canary deployments on deploy board](img/deploy_boards_canary_deployments_v9_2.png)
 
 #### How to check the current traffic weight on a Canary Ingress (deprecated)
 
@@ -106,7 +106,7 @@ This feature was [deprecated](https://gitlab.com/groups/gitlab-org/configure/-/e
 1. Visit the [deploy board](../../user/project/deploy_boards.md).
 1. View the current weights on the right.
 
-   ![Rollout Status Canary Ingress](img/canary_weight.png)
+   ![Rollout Status Canary Ingress](img/canary_weight_v13_7.png)
 
 #### How to change the traffic weight on a Canary Ingress (deprecated)
 

doc/user/project/deploy_boards.md

@@ -41,7 +41,7 @@ With deploy boards you can gain more insight into deploys with benefits such as:
 
 Here's an example of a deploy board of the production environment.
 
-![deploy boards landing page](img/deploy_boards_landing_page.png)
+![deploy boards landing page](img/deploy_boards_landing_page_v9_0.png)
 
 The squares represent pods in your Kubernetes cluster that are associated with
 the given environment. Hovering above each square you can see the state of a
@@ -111,7 +111,7 @@ To display the deploy boards for a specific [environment](../../ci/environments/
 
    If you use GCP to manage clusters, you can see the deployment details in GCP itself by navigating to **Workloads > deployment name > Details**:
 
-   ![deploy boards Kubernetes Label](img/deploy_boards_kubernetes_label.png)
+   ![deploy boards Kubernetes Label](img/deploy_boards_kubernetes_label_v11_9.png)
 
 Once all of the above are set up and the pipeline has run at least once,
 go to the environments page under **Operate > Environments**.

doc/user/project/import/bitbucket.md

@@ -102,7 +102,7 @@ For user contributions to be mapped, each user must complete the following befor
 1. Select **Bitbucket Cloud**.
 1. Sign in to Bitbucket and grant GitLab access to your Bitbucket account.
 
-   ![Grant access](img/bitbucket_import_grant_access.png)
+   ![Grant access](img/bitbucket_import_grant_access_v8.png)
 
 1. Select the projects that you'd like to import or import all projects.
    You can filter projects by name and select the namespace

doc/user/project/import/fogbugz.md

@@ -38,9 +38,9 @@ To import your project from FogBugz:
 1. Select **FogBugz**.
 1. Enter your FogBugz URL, email address, and password.
 1. Create a mapping from FogBugz users to GitLab users.
-   ![User Map](img/fogbugz_import_user_map.png)
+   ![User Map](img/fogbugz_import_user_map_v8.png)
 1. For the projects you want to import, select **Import**.
-   ![Import Project](img/fogbugz_import_select_project.png)
+   ![Import Project](img/fogbugz_import_select_project_v8.png)
 1. After the import finishes, select the link to go to the project
    dashboard. Follow the directions to push your existing repository.
 1. To import a project:

doc/user/project/issue_board.md

@@ -412,7 +412,7 @@ them to change their position and epic assignment:
 - To remove an issue from an epic, drag it to the **Issues with no epic assigned** lane.
 - To move an issue to another epic _and_ another list, at the same time, drag the issue diagonally.
 
-![Drag issues between swimlanes](img/epics_swimlanes_drag_and_drop.png)
+![Drag issues between swimlanes](img/epics_swimlanes_drag_and_drop_v13_6.png)
 
 ## Work in progress limits
 

doc/user/project/issues/crosslinking_issues.md

@@ -67,7 +67,7 @@ When mentioning issue `#111` in issue `#222`, issue `#111` also displays a notif
 in its tracker. That is, you only need to mention the relationship once for it to
 display in both issues. The same is valid when mentioning issues in [merge requests](#from-merge-requests).
 
-![issue mentioned in issue](img/mention_in_issue.png)
+![issue mentioned in issue](img/mention_in_issue_v9_3.png)
 
 ## From merge requests
 
@@ -79,7 +79,7 @@ When you mention an issue in a merge request description, it
 you can also [set an issue to close automatically](managing_issues.md#closing-issues-automatically)
 as soon as the merge request is merged.
 
-![issue mentioned in MR](img/mention_in_merge_request.png)
+![issue mentioned in MR](img/mention_in_merge_request_v9_3.png)
 
 ## From branch names
 

doc/user/project/issues/due_dates.md

@@ -22,13 +22,13 @@ appear for choosing the date. To remove the date, select the date
 text and delete it. The date is related to the server's time zone, not the time zone of
 the user setting the due date.
 
-![Create a due date](img/due_dates_create.png)
+![Create a due date](img/due_dates_create_v9_3.png)
 
 You can also set a due date by using the issue sidebar. Expand the
 sidebar and select **Edit** to pick a due date or remove the existing one.
 Changes are saved immediately.
 
-![Edit a due date with the sidebar](img/due_dates_edit_sidebar.png)
+![Edit a due date with the sidebar](img/due_dates_edit_sidebar_v9_3.png)
 
 The last way to set a due date is by using [quick actions](../quick_actions.md), directly in an issue's description or comment:
 
@@ -45,7 +45,7 @@ To display issues with the latest due dates at the top, select **Sort direction*
 
 Due dates also appear in your [to-do list](../../todos.md).
 
-![Issues with due dates in the to dos](img/due_dates_todos.png)
+![Issues with due dates in the to dos](img/due_dates_todos_v9_3.png)
 
 The day before an open issue is due, an email is sent to all participants
 of the issue. Like the due date, the "day before the due date" is determined by the