add fsGroup and or supplementalGroups to all relevant kube examples for consistency

[jmccormick2001]

fsGroup and or supplementalGroups

to avoid persistent disk issues, the use of fsGroup and/or supplementalGroups is used
in the spec examples....all of the kube/ose examples need to reflect this.

[jmccormick2001]

use this when NFS is the storage type, set the group IDs to match that of the NFS group ID...

"supplementalGroups": [
5555,
6666
]

for NFS , supplementalGroups is the method to use, not fsGroup, for block storage use fsGroup...confusing? surely not!

[jmccormick2001]

merged, now all NFS examples will use supplementalGroups, the OSE dedicated will use fsGroup since those are targeted towards a Dedicated envionrment that uses AWS block storage which requires fsGroup instead. The dedicated template examples could be duplicated to provide a set of templates for non-block storage at some future point.