Remove flaky check.

[sopel39]

dictionary_page_offset might not be reliable, even when dictionary encoding is present.

Description

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

Fixes #27232

[sopel39]

https://stackoverflow.com/questions/55225108/why-is-dictionary-page-offset-0-for-plain-dictionary-encoding

[raunaqmorarka]

I'm not sure this will address the problem
If a column uses dictionary encoding, then it must write a dictionary page and that has to be a non-zero offset from beginning of file (because parquet file has a compulsory header of few bytes).
So if this was failing sometimes, then the next check for use of dictionary encoding should also fail, as the dictionary page offset can be zero only if there is no dictionary page at all.

[sopel39]

I cannot really reproduce the issue locally.

Take a look at https://stackoverflow.com/a/55226688.

If a column uses dictionary encoding, then it must write a dictionary page and that has to be a non-zero offset from beginning of file (because parquet file has a compulsory header of few bytes).

Assuming that example is correct (where parquet-mr puts 0 even when dictionaries are present), does it mean we do not support dictionary offset correctly?