fix: make mixed CRUD method directives order-independent

[014-code]

Summary

Fixes #809.

Mixed CRUD requests containing @post, @put, or @delete could be parsed incorrectly depending on the order of fields in the JSON object.

For example, when a business object appeared before its @delete directive, the object could fall back to GET or use the method assigned to a related array entry.

Root Cause

AbstractParser.batchVerify collected method directives and processed business objects in the same loop.

Therefore, a directive only affected objects appearing after it in iteration order.

Changes

• Pre-scan all supported method directives before processing business objects
• Make mixed CRUD method dispatch independent of JSON field order
• Preserve the priority of an object's explicit @method
• Keep method directive values limited to String or JSONObject
• Add documentation for deleting and batch inserting into the same table
• Add regression tests for method ordering, priority, and invalid array values

Verification

• mvn -q -f APIJSONORM/pom.xml test
• Tests run: 3
• Failures: 0
• Errors: 0
• git diff --check passed