Disable logical type cast of fastavro

[DKER2]

fix #31656

The bug is caused by the fact that when fastavro library read avro file with logicaltype, it will try to cast it to native type in python. For example, when avro field has long type and logical type is timestamp-millis, they will try cast orignal timestamp into datetime. Example cast from fastavro is attached in the image

---

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.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @claudevdm for label python.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[DKER2]

When I am trying to add test coverage by adding logical type field in RECORDS. This unit test failed, but by reading the test, I do not understand what is 14.5 constant. So I have not add in tests

[claudevdm]

When I am trying to add test coverage by adding logical type field in RECORDS. This unit test failed, but by reading the test, I do not understand what is 14.5 constant. So I have not add in tests

Can you just extend or use a new list of records to test this fix (don't change the shared RECORDS)?

[claudevdm]

This will remove all avro LOGICAL_READERS in both the case where someone outputs as_row, or not meaning whatever the atomic value of the logical type is will be passed and all other info will be lost..

This might break for people who depend on the current LOGICAL_READERS behavior when as_row=False. If we decide to pass timsetamp-millis as integers, a more targeted fix would be to remove the LOGICAL_READER for 'long-timestamp-millis' only if as_row=True.

Also worth considering whether we want to treat the "timestamp-millis" as a Timestamp like mentioned in #31656 (comment).

@Abacn do you have an opinion whether the "timestamp-millis" type should be treated as an integer or a "Timestamp" type?

[Abacn]

Yeah agree, a generic suggestion is to avoid breaking change to users.