fix: improve inline objects naming by adding the path to the name

Created by: simllll

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh

  Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH.
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

Right now all InlineObjects are just named InlineObject1,2,3... this improves the naming for the requestBody and response where this happens the most (at least in our setup). In case there is no title, it adds the current path to the inline object. This improves the output a lot and also ensures more consistency between api client generations. Everytime there is a new endpoint, the inline object enumration was different, now it stays consistent, regardless if there is an endpoint added, modified or removed.

fixes #4399

This apparoch could probably applied to more places where resolveModelName is used.