Rename Pagure migration images to descriptive filenames and crop screenshots

- Renamed migration_pagure_08.png to pagure_migration_new_migration_button.png
- Renamed migration_pagure_09.png to pagure_migration_select_pagure_source.png
- Renamed migration_pagure_10.png to pagure_migration_form_filled.png
- Renamed migration_pagure_11.png to pagure_migration_start_migration_button.png
- Renamed migration_pagure_12.png to pagure_migration_completion_success.png

- Cropped screenshots to remove empty space and unneeded bloat for cleaner documentation

Updated references in both pagure_repository.adoc and pagure_private_tickets.adoc
to use the new descriptive filenames that clearly indicate image content.

Signed-off-by: Ryan Lerch <rlerch@redhat.com>

modules/ROOT/pages/migration/pagure_private_tickets.adoc

@@ -67,9 +67,9 @@ The private ticket migration process involves four main steps: creating a Pagure
 . Navigate to the destination organization where you want to create the private repository.
    image:migration_pagure_07.png[]
 . Click on the *New migration* button to begin the migration process.
-   image:migration_pagure_08.png[]
+   image:pagure_migration_new_migration_button.png[]
 . Click on the *Pagure* button at the bottom of the migration page.
-   image:migration_pagure_09.png[]
+   image:pagure_migration_select_pagure_source.png[]
 
 === Configure Private Repository Migration
 

modules/ROOT/pages/migration/pagure_repository.adoc

@@ -48,13 +48,11 @@ The migration process involves two main steps: accessing the Fedora Forge migrat
 
 === Access Fedora Forge Migration Tool
 
-. Log into Fedora Forge using your Fedora Account credentials.
-. Navigate to the destination organization where you want to create the migrated repository.
-   image:migration_pagure_07.png[]
+. Log into Fedora Forge using your Fedora Account credentials and navigate to the destination organization where you want to create the migrated repository.
 . Click on the *New migration* button to begin the migration process.
-   image:migration_pagure_08.png[]
+   image:pagure_migration_new_migration_button.png[]
 . Click on the *Pagure* button at the bottom of the migration page.
-   image:migration_pagure_09.png[]
+   image:pagure_migration_select_pagure_source.png[]
 
 === Configure Repository Migration
 
@@ -63,17 +61,18 @@ The migration process involves two main steps: accessing the Fedora Forge migrat
 .. *Clone URL:* Enter the Git clone URL from your Pagure repository
 .. *Description:* Copy the repository description from Pagure (optional)
 .. *Visibility:* Set to public for publicly accessible content
-   image:migration_pagure_10.png[]
-. **Leave the token field empty** - this is crucial for standard repository migration.
+.. **Leave the token field empty** - this is crucial for standard repository migration.
+   image:pagure_migration_form_filled.png[]
 +
 [WARNING]
 ====
 **Do NOT enter an API key in the token field.** If you provide an API key here, the migrator will only import private tickets instead of the full repository content (code, public issues, pull requests, etc.). This will result in an incomplete migration. Additionally, if you haven't set the repository to private, these private tickets will become publicly visible, potentially exposing confidential information.
 ====
+
 . Click on the *Migrate repository* button to start the migration.
-   image:migration_pagure_11.png[]
+   image:pagure_migration_start_migration_button.png[]
 . Wait for the migration to complete. This creates a repository with all publicly accessible data.
-   image:migration_pagure_12.png[]
+   image:pagure_migration_completion_success.png[]
 
 == Verification