Added
* added editation of resource instance attributes
* added display of constraints of resource inside resource detail
* resource status
  * more detailed information in resource tree view
  * crm statuses in resource detail
* added empty states (when there is no relevant data)
  * in dashboard - no issue, no resource, no fence device
  * in cluster detail - no resources, no fence devices, resource does not exists
* added resource agent description to resource detail
* added list-detail view of nodes and fence devices
* added information table about node services to node detail
* added crm statuses of resources running on particular node in node detail
* changed loading of dashboard to independent loading of each cluster

Following bugs will be included in bz1845470

[root@virt-125 ~]# rpm -q pcs
pcs-0.10.6-3.el8.x86_64


## Adding resources and constraint

[root@virt-125 ~]# pcs resource create dummy1 ocf:heartbeat:Dummy
[root@virt-125 ~]# pcs resource create dummy2 ocf:heartbeat:Dummy

[root@virt-125 ~]# pcs constraint order start dummy1 then dummy2
Adding dummy1 dummy2 (kind: Mandatory) (Options: first-action=start then-action=start)


## in web UI

# log into the web UI (e.g. https://virt-125.cluster-qe.lab.eng.brq.redhat.com:2224/ui/)
# Add existing cluster
# Click on 'Resources'
# Click on 'dummy1'
# Click on 'Full description'
	> OK: A resource agent description is present
# On the same page 'Resource status on nodes', contains this info: Node, Active, Failed, Blocked, Managed, Target role, Role, Failure ignored, Nodes running on
	> OK: A detailed resource status is present

# Creating clone
[root@virt-125 ~]# pcs resource clone dummy1
> OK, 'Resource status on nodes' shows status on both nodes, on which the resource is running, automatically created a 'dummy1-clone' resource, above 'dummy1' in resource display

# Click on 'Attributes' within dummy1
	> OK: Attributes are present with actual values and description
# Click 'Edit Attributes'
# Changing 'fake' attribute
	> OK: The attribute is changed after few seconds

# Click on 'Constraints' within dummy1-clone
	> OK: The constraint is present:
	Type Order
	Before dummy2
	Kind Mandatory

# Click on 'Nodes' in the menu
	> OK: Both nodes are in the list and have 'Status' and 'Quorum' state
# Click on one of the nodes (virt-125 in this case) 
	> OK: In the detail, there is information about Resources on node, Node Daemnos (corosync, pacemaker, pcsd, sbd) and Pacemaker

# Click on 'Fence Devices'
	> OK: The fence devices are present in the list, so far without any details

# Click on 'Clusters' to get dashboard
	> OK: The cluster is present in list, with zero Issues, 2 Nodes, 2 Resources and 2 Fence devices

# Removing resources and fence devices
[root@virt-125 ~]# pcs resource delete dummy1
Attempting to stop: dummy1... Stopped
[root@virt-125 ~]# pcs resource delete dummy2
Attempting to stop: dummy2... Stopped
[root@virt-125 ~]# pcs property set stonith-enabled=false
[root@virt-125 ~]# pcs resource delete fence-virt-125
Attempting to stop: fence-virt-125... Stopped
[root@virt-125 ~]# pcs resource delete fence-virt-126
Attempting to stop: fence-virt-126... Stopped


# Click on "Clusters" to get dashboard
	> Cluster in present in list, with 2 Issues ('No fencing configured in the cluster' and 'Stonith is not enabled'), 2 Nodes, 0 Resources, 0 Fence devices

# Click on the cluster
# Click on 'Resources'
	> OK:
	'No resource is configured.
	You don't have any configured resources here.'
# Click on 'Fence Device'
	> OK:
	'No fence device is configured.
	You don't have any configured fence device here.'


Additional features will be added in the next release, tracking bz: bz1845470
Marking as VERIFIED for pcs-0.10.6-3.el8

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (pcs bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4617