Pacemaker's "db2" resource fails to start due to database not being in a HADR configuration

Issue

Pacemaker's db2 resource agent fails start operations and the below error can be observed in standard logs:

$ cat /var/log/messages
------------------------------------->8--------------------------------------
Apr 26 09:03:38 node01 db2(db2_resource)[####]: ERROR: DB2 database instance/db is not in a HADR configuration but I am a M/S resource
Apr 26 09:03:38 node01 crmd[####]:  notice: Result of start operation for db2_resource on node01: 5 (not installed)
Apr 26 09:03:38 node01 crmd[####]: warning: Action 7 (db2_resource_start_0) on node01 failed (target: 0 vs. rc: 5): Error

An error of not installed can be observed from pcs status output:

$ pcs status --full
------------------------------------->8--------------------------------------
Failed Resource Actions:
* db2_resource_start_0 on node01 'not installed' (5): call=498, status=complete, exitreason='',
    last-rc-change='Tue Apr 26 09:03:34 2022', queued=1ms, exec=4455ms