[Issue] Remove 'version' manipulation from sampledata:deploy, improve success messaging

[m2-assistant]

This issue is automatically created based on existing pull request: #36187: Remove 'version' manipulation from sampledata:deploy, improve success messaging

---

Description

When running bin/magento sampledata:deploy, an error message is shown regarding a missing version key in composer.json. The linked page provided in the error message says that version should not be present in composer.json. The sampledata:deploy command then tries to add a 'version' key to composer.json with varying degrees of success. When this is coupled with the lack of success message, developers are left wondering if the command was successful or not. The 'version' string within composer.json is not required nor used by anything in this module, and should not be present.

This pull request adds a success message and instructions on what to do next for developers to follow when the command is successful, and removes any manipulation of 'version' within composer.json.

Manual testing scenarios

No success message

1. Run bin/magento sampledata:deploy
2. Witness (lack of) success messaging when the command completes successfully

'version' requirement in composer.json

1. Ensure that composer.json has no version key (according to Composer best practices)
2. Run bin/magento sampledata:deploy
3. Witness (lack of) error messaging and (lack of) changes in composer.json

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-7300 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Lima. Thank you for verifying the issue.
Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.