add log hint in modules create and add create containers to modules bump-versions

[mashehu]

Partially taken from #4362 (everything except of running the container creation during modules creation)

[codecov]

Codecov Report

❌ Patch coverage is 80.35714% with 33 lines in your changes missing coverage. Please review.
✅ Project coverage is 78.81%. Comparing base (e3dbb4f) to head (40fe733).
⚠️ Report is 1 commits behind head on dev.

Files with missing lines	Patch %	Lines
nf_core/modules/bump_versions.py	83.90%	14 Missing ⚠️
nf_core/commands_modules.py	0.00%	13 Missing ⚠️
nf_core/modules/containers.py	90.90%	6 Missing ⚠️

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[JulianFlesch]

Is this the correct log level we want? Does this always show?

[mashehu]

yes, should always hint to use that after the creation of the module for now. later we will actually do this step here.

[JulianFlesch]

Suggested change

	(docker/singularity × platform) that :meth:`ModuleContainers.create` renders when a
	(docker/singularity x platform) that :meth:`ModuleContainers.create` renders when a

[mashehu]

\cross is the right symbol here 🤓

[JulianFlesch]

I am not sure if I like these static functions when they are heavily parametrized and not helping to instantiate objects, but rather expecting them as input.
They are obviously useful to simplify one specific complex flow, but here we expect a manager, components and then also the Path.

Can we redesign this a bit such that it e.g. only requires a Path and a Module name (str)?

[JulianFlesch]

build_containers_with_progress lives in the same module as ModuleContainers so it is fair to assume knowledge about its instantiation. This would reduce that coupling in more distant logic that lives in command_modules etc.

[mashehu]

good idea

[JulianFlesch]

We never pass force when building containers from this class. Should we resurface this?

[codspeed-hq]

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

✅ 8 untouched benchmarks

---

_{Comparing mashehu:add-container-create-info (40fe733) with dev (facc035)}