Fix beam.Row.__eq__ to ignore key order

[Polber]

Beam Rows in the Python SDK are compared using an __eq__ method that considers the position of each key in the row. The case should be that order does not matter so long as all keys exists and have equal values of equal types.

Fixes #32832

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[robertwb]

I'm not positive we want comparison to be order-independent, see e.g. the comments on #23876

[Polber]

I'm not positive we want comparison to be order-independent, see e.g. the comments on #23876

Yeah it appears I totally missed a crucial comment

Note that in Beam 2.30.0 and later, Row objects are sensitive to field order.
So `Row(x=3, y=4)` is not considered equal to `Row(y=4, x=3)`.

It seems odd to me that order should matter on a schema'd data type, but I presume there is a use-case I'm not considering. In any case, I opened #32851 to fix the failing YAML tests

[Polber]

Closing in favor of #32851