PUT new attribute backwards compatibility optional

https://github.com/OpenAPITools/openapi-diff/issues/136 made the PUT request incompatibility check stricter, considering an additional field as a breaking change. This makes sense for a scenario where updates are taking place, but is too strict if PUTs represent only inserts.

What would be the best way of optionally removing the strict handling of PUTs? Options could include:

• Surfacing more information about how the changedOperation.isIncompatible() decision was made, allowing the user of the OpenApiDiff to use more granular information to decide whether it should be considered as a breaking change.
• Adding a command-line flag to remove the PUT strictness for all cases in a run.
• Writing some code to traverse the object graph for PUTs when the diff has completed and decide whether the strict PUT handling is what caused the incompatibility, and then ignore it.

首先跟踪 changedOperation.isIncompatible() 如何处理 PUT 请求中的新增字段，以及该结果如何传递到已完成的 diff。比较提议的方法：公开粒度更细的不兼容信息、添加命令行标志，或在 diff 之后遍历对象图。完成的标准是明确指定一个选定的设计，并涵盖其对仅插入型 PUT 和更新型 PUT 的行为。