Please fill in the following information:

Issue description

The storage section (and GE and labs) are missing some important updates to the Ansible storage modules that have transpired since this was originally written in 2019. This makes storage management seem more complicated than it really is.

The most crucial problem is omission of the community.windows.win_initialize_disk module. The exercises use a direct PowerShell command instead which is bad practice. Use of win_initialize_disk would also make the exercises simpler, since the module is idempotent and there's no need to check for existence of a GUID using ansible facts.

Speaking of facts, the exercise also uses an unnecessary JSON filter to extract the second disk by number. This was needed back in Ansible 2.8 where the win_disk_facts module did not sort properly but was fixed a while ago; see https://github.com/ansible/ansible/pull/64997