scaleway_organization_info: sanity checks

[russoz]

SUMMARY

Fix sanity checks.

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

plugins/modules/scaleway_organization_info.py

[ansibullbot]

cc @QuentinBrosse @Spredzy @abarbare @jerome-quere @kindermoumoute @remyleone @sieben
click here for bot help

[github-actions]

Docs Build 📝

Thank you for contribution!✨

This PR has been merged and your docs changes will be incorporated when they are next published.

[patchback]

Backport to stable-5: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 83ff442 on top of patchback/backports/stable-5/83ff4429e887c89edfb7f6c494d2a755fd75a3fd/pr-5571

Backporting merged PR #5571 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/community.general.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-5/83ff4429e887c89edfb7f6c494d2a755fd75a3fd/pr-5571 upstream/stable-5

4. Now, cherry-pick PR scaleway_organization_info: sanity checks #5571 contents into that branch:

   $ git cherry-pick -x 83ff4429e887c89edfb7f6c494d2a755fd75a3fd

   If it'll yell at you with something like fatal: Commit 83ff4429e887c89edfb7f6c494d2a755fd75a3fd is a merge but no -m option was given., add -m 1 as follows intead:

   $ git cherry-pick -m1 -x 83ff4429e887c89edfb7f6c494d2a755fd75a3fd

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR scaleway_organization_info: sanity checks #5571 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-5/83ff4429e887c89edfb7f6c494d2a755fd75a3fd/pr-5571

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-6: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-6/83ff4429e887c89edfb7f6c494d2a755fd75a3fd/pr-5571

Backported as #5577

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[felixfontein]

@russoz thanks!