Use 'Object.hasOwn()' instead of 'Object.prototype.hasOwnProperty.call()'

[batchu5]

A SonarQube cloud issue - https://sonarcloud.io/project/issues?open=AZjwsV_WFWmyNdBGS5UA&id=asyncapi_generator

Approach replace Object.prototype.hasOwnProperty.call() with Object.hasOwn()

[derberg]

here is discussion on why it was implemented this way: #1769

you can open a PR that adds comment why it is this way and add proper sonar annotation to make sonar stop complaining about it. I do not remember how it is done, you can check existing code pace, #NOSONAR I think but dunno if that works

[batchu5]

hey @derberg, please check the issues, #1913 #1914 #1915. They are also SonarQube Cloud issues, so should I add the #NOSONAR
to them also? As this is a small PR, I think that it would be better if I include all of them in one PR.

[Adi-204]

@batchu5 for now can you please create PR for only this issue. For other sonar issues will need to look and will take some time additionally already many other issues in the repo thanks!