fix: Fix DML ON clause for imperative statements

[Nurkambay]

Checklist:

• Each of my commits contains one meaningful change
• I have performed rebase of my branch on top of the development
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have checked my code and corrected any misspellings

[Nurkambay]

According to the IDMS team information, all ON causes must generate IF statement with a PERFORM IDMS-STATUS statement.

• IDMS tests updated according to this changes
• New US to support COPY IDMS IDMS-STATUS. created.

[VitGottwald]

Adding a link to the IDMS documentation for future reference:

As documented in AUTOSTATUS Protocols. the ON clause can be used on any DML statement except an IF DML statements (IF MEMBER , IF EMPTY). The COBOL IF for the ON clause will be generated the same exact way for every DML .

[Nurkambay]

Link to imperative statements list:
https://www.ibm.com/docs/en/cobol-zos/6.4?topic=categories-imperative-statements

[Nurkambay]

I have excluded DELETE statement from the generating IF statement process