Support data disk mounting

[ox-warrior]

What would you like to be added:
support data disk mounting
Why is this needed:
Only the system disk is supported, and the mounting of data disks, especially multiple data disks, is not supported. This is particularly unfriendly in scenarios that require multiple data disks, such as Elasticsearch (Es) and Alluxio.
Completion requirements:

The artifacts should be linked in subsequent comments.

[jwcesign]

We will put this into roadmap

[daimaxiaxie]

While we have implemented basic support for data disks, the current architecture maintains separate formats for system disks and data disks. We should standardize the formats of system disks and data disks to enhance compatibility and ease of management.

New

// SystemDisk to be applied to provisioned nodes.
// +optional
SystemDisk *Disk `json:"systemDisk,omitempty"`
// This item is mutually exclusive with disk.Category
// +optional
SystemDisksCategories []string `json:"systemDiskCategories,omitempty"`
// DataDisk to be applied to provisioned nodes.
// +optional
DataDisks []*Disk `json:"dataDisks,omitempty"`
// The category of the data disk (for example, cloud and cloud_ssd).
// Different ECS is compatible with different disk category, using array to maximize ECS creation success.
// Valid values:"cloud", "cloud_efficiency", "cloud_ssd", "cloud_essd", "cloud_auto", and "cloud_essd_entry"
// +kubebuilder:validation:Items=Enum=cloud;cloud_efficiency;cloud_ssd;cloud_essd;cloud_auto;cloud_essd_entry
// +optional
DataDisksCategories []string `json:"dataDiskCategories,omitempty"`

type Disk struct {
       Category *string
       Size *int32
       PerformanceLevel *string
       Device *string
}

further

// Disk to be applied to provisioned nodes.
// +optional
Disks []*Disk `json:"disks,omitempty"`
// This item is mutually exclusive with disk.Category
// +optional, 
DisksCategories []string `json:"diskCategories,omitempty"`

type Disk struct {
       Category *string
       Size *int32
       PerformanceLevel *string
       Device *string
       SystemDisk bool
}

[jwcesign]

If Disk.Category is nil, the system will fall back to DataDisksCategories?

[daimaxiaxie]

If Disk.Category is nil, the system will fall back to DataDisksCategories?

Yes, I want to prioritize DataDisksCategories, and if empty use Disk.Category. (Priority can be discussed later)
And try to ensure that Categories and Category are mutually exclusive, only one of them is allowed to be filled in.

[jwcesign]

If we want something like priority, we can order the value in DataDisksCategories , and then, filed Category is not needed.

What's the scenario?

[daimaxiaxie]

The priority I mentioned refers to DataDisksCategories and Disk.Category, which one is used first.

Also to add, when using Disk.Category, we will abandon the DataDisksCategories/SystemDisksCategories multi-selection.