"The specified vg_access_mode doesn't match the lock_type on VG metadata!" observed after creating `LVM-activate` cluster resources using `vg_access_mode=system_id`

Issue

• After creating the cluster resource LVM-activate using the vg_access_mode=system_id option, it gives an error pointing the vg_access_mode as incorrect and the LVM-activate resource fails to start:

  # pcs status
  ...
  Full List of Resources:
    * Resource Group: splunkdb:
      * lvm-rsc   (ocf::heartbeat:LVM-activate):   Stopped
      * fs_rsc    (ocf::heartbeat:Filesystem):     Stopped
  
  Failed Resource Actions:
    * lvm-rsc_start_0 on node1 'not configured' (6): call=32, status='complete', exitreason='The specified vg_access_mode doesn't match the lock_type on VG metadata!', last-rc-change='Fri May  3 10:38:41 2024', queued=0ms, exec=201ms