Redfish Resources to help represent Drive

I am looking into ways to represent a Drive and is wondering how I would be able to represent some of the more specific information.

Some of the information that I am thinking about includes the following along with my proposal of how to fix it.

- Watchdog
    - Watchdog Triggered
    - Disable/Enable Watchdog

Create a new Watchdog Resource that can be used to manage the watchdog for the Drive. It should be the similar as HostWatchdogTimer for ComputerSystem. It should just be able to monitor the watchdog state and trigger them if needed.

- Boot Failure Count
Add a property under Drive to keep count? or in somewhere else that is common.

- Boot Image Select
Similar to github.com/DMTF/Redfish/issues/3357 where we can select different image to boot from... but for Drive instead of BIOS. Being able to select the image to bootup with.

----

For the topics above, it seems like it can be covered by ComputerSystem + BIOS.

Can Drive or other hardware resources be consider a ComputerSystem? then we can keep all the properties under ComputerSystem and not duplicate it for all the different hardwares.

-----

Other property that I am considering,

- Drive Operation Mode
    - Different operation mode that the drive can be in.
    - The State.State does not represents it since it is limited to represent one thing at a time.
    - I am thinking of cases where multiple operating mode in enabled at the same time.
    - For example, Manufacturing mode and Debug mode
        - Can be in both debug and Manufacturing mode.

Add a new property under Drive with a list of OperatingModes

```
{

    {Name: "Manufacturing", Enabled: true},
    {Name: "Debug", Enabled: true}

}
```

- PowerSignal
    - States for different power signals. PowerGood
I had some discussion in github.com/DMTF/Redfish/issues/4523, but this different than what the issue is about.

But thinking about a new resource call PowerSignal that can be linked from other resources. Each property can contain state of the power signal.

```
PowerSignal {
    Name: "power0",
    PowerGood: true
}
```

- Power Sequence State
    - The power sequence state can be really specific and not easy to represent in Redfish.
    - The number of state can vary between hardwares
    - We can either represent it as a free string or an encoded number. (both are not ideal)

Probably in OEM property?

----

That's mostly what I have for now. Please let me know if any of this is possible or going in the wrong direction.