Documentation: Clarify module naming during transition period (v2.5.0)

[hodie-aurora]

Issue Type: Documentation Enhancement

Description:

I ran into some confusion while working with the ngine_io.cloudstack collection v2.5.0. There seems to be a mismatch between what the documentation suggests and what actually works in practice.

The Problem:

Here's what I discovered: The runtime.yml:56 lists zone_info in the action groups, and runtime.yml:321-325 shows there should be a redirect from cs_zone_info to ngine_io.cloudstack.zone_info.

However, when I tried using ngine_io.cloudstack.zone_info in my playbooks, Ansible consistently failed with:

ERROR! couldn't resolve module/action 'ngine_io.cloudstack.zone_info'
The only way I could get it working was by using the legacy name ngine_io.cloudstack.cs_zone_info, which matches the actual filename in the modules directory.

Environment:

Collection version: 2.5.0
Ansible version: 2.16.11
Python version: 3.10.12

What I Expected:
Either the redirect mechanism should work seamlessly across different Ansible setups, or the documentation should be clearer about which module names to actually use in the current version.

I appreciate your consideration of this issue, and thank you for all your hard work on this project.