EXP: [Python] Narrow pyarrow.feather deprecation to Feather V1 format

[tadeja]

Rationale for this change

Prototype, potential follow-up to #49232 / #49590

What changes are included in this PR?

Remove warnings from write_feather(), read_feather(), read_table(), and FeatherDataset.
Warn on writing with version=1 / reading Feather V1 file
Update docs to V1-only and keep IPC migration guide
Additionally corrected notes like deprecated as of 24.0.0 to 25.0.0 instead

Are these changes tested?

Yes, on fork CI jobs succeed (except for unrelated macOS segmentation fault as it's also seen on main since commit 5e698fe )

Are there any user-facing changes?

Yes ...

[github-actions]

Thanks for opening a pull request!

This pull request has been automatically converted to a draft because its title doesn't match Arrow's required format.

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

After updating the title, you can mark the pull request as ready for review.

See also:

• Other pull requests
• Contribution Guidelines - Contributing Overview