fix: raid_level defined by disk_count.

[RSabounds]

current raid configuration functions based on build using only two disks. This fix will apply a raid_level based on # of disks present in the controller.
Options are 0, 1, 5.

Testing locally is successful. testing in container actively working on.

[RSabounds]

local@local:$ docker run --rm -u root -it --env-file env_vars.txt test_image:latest get-raid-devices --ip-address 1.2.3.4
{"logical_disks": [{"controller": "RAID.Integrated.1-1", "is_root_volume": true, "physical_disks": ["Disk.Bay.0:Enclosure.Internal.0-0:RAID.Integrated.1-1", "Disk.Bay.1:Enclosure.Internal.0-0:RAID.Integrated.1-1", "Disk.Bay.2:Enclosure.Internal.0-0:RAID.Integrated.1-1", "Disk.Bay.3:Enclosure.Internal.0-0:RAID.Integrated.1-1", "Disk.Bay.4:Enclosure.Internal.0-0:RAID.Integrated.1-1", "Disk.Bay.5:Enclosure.Internal.0-0:RAID.Integrated.1-1"], "raid_level": "5", "size_gb": "MAX"}]}
local@local:$ docker run --rm -u root -it --env-file env_vars.txt test_image:latest get-raid-devices --ip-address 2.3.4.5
{"logical_disks": [{"controller": "RAID.SL.1-1", "is_root_volume": true, "physical_disks": ["Disk.Bay.0:Enclosure.Internal.0-1:RAID.SL.1-1", "Disk.Bay.1:Enclosure.Internal.0-1:RAID.SL.1-1"], "raid_level": "1", "size_gb": "MAX"}]}

test with updated script adjusts raid level based on number of disks present.
Options: 0= 1disk, 1= 2 disks, 5= >2 disks