docs: document deprecation rationale for getPomFile/setPomFile

[anukalp2804]

Fixes #11674

Documents the deprecation rationale and recommended replacement for the model API methods getPomFile() and setPomFile(File).

This change is documentation-only and does not affect runtime behavior.

Build: mvn -DskipTests -pl api/maven-api-model -am verify

Following this checklist to help us incorporate your
contribution quickly and easily:

• Your pull request should address just one issue, without pulling in other changes.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
  This may not always be possible but is a best-practice.
• Run mvn verify to make sure basic checks pass.
  A more thorough check will be performed on your pull request automatically.
• You have run the Core IT successfully.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[cstamas]

This is again wrong, version 4.0.0 of Maven was not even released.

[anukalp2804]

Thanks — you’re right. I’ve replaced the JavaDoc link with plain text in the .mdo file and kept the deprecation version-agnostic.

[elharo]

This is pulling in changes from other PRs. remove from this PR

[anukalp2804]

Thanks for catching that — I’ve removed the unrelated Language.java changes so this PR now only contains the maven.mdo updates.

[elharo]

but it's once again including redundant info

[elharo]

needs to sync with master

[anukalp2804]

needs to sync with master

Rebased this branch on the latest upstream/master and resolved conflicts in Language.java. The previous changes were already present upstream, so duplicate commits were skipped to keep the history clean. Force-pushed the updated branch to sync the PR.

[elharo]

but it's once again including redundant info

[anukalp2804]

Thanks for the note. I kept a single @deprecated entry in the Javadoc with only the replacement reference, since the version is already specified via @Deprecated(since = "4.0.0"). Please let me know if you’d prefer a different format.

[elharo]

now you've lost since in the annotation

[anukalp2804]

Thanks for catching that. I’ve restored the since = "4.0.0" value in the @Deprecated annotation and kept a single Javadoc @deprecated entry with the replacement reference.

[desruisseaux]

We lost the {@link} with this change.

[anukalp2804]

Good catch, thanks. I’ve restored the {@link} reference in the deprecation Javadoc so the method remains properly linked.

[github-actions]

@elharo Please assign appropriate label to PR according to the type of change.

[anukalp2804]

Thank you for the review and merge 🙂