400.001 and 400.002 alarms tagged as Openstack should be StarlingX

[Agustin Carranza]

Brief Description
-----------------
The alarms "400.001/400.002" are raised on platform (e.g. when one controller is locked in the AIO-DX system). But, the documentation does not list these alarms on the page of "400 Series Alarm Messages". https://docs.starlingx.io/fault-mgmt/kubernetes/400-series-alarm-messages.html

Severity
--------
Minor: System/Feature is usable with minor issue

Steps to Reproduce
------------------
Check documentation

Expected Behavior
------------------
400.001 and 400.002 alarms are tagged as StarlingX.

Actual Behavior
----------------
400.001 and 400.002 alarm are tagged as Openstack.

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
N/A

Branch/Pull Time/Commit
-----------------------
N/A

Last Pass
---------
N/A

Timestamp/Logs
--------------
N/A

Test Activity
-------------
Normal use

Workaround
----------
N/A

[John Kung (john-kung)]

The following has been merged into stx-master and stx 8.0. (Although LP isnt currently being automatically updated).

stx8.0 https://review.opendev.org/c/starlingx/fault/+/889323
master https://review.opendev.org/c/starlingx/fault/+/889182