innochecksum fails to validate full_crc32 for compressed or encrypted tables

The innodb_checksum_algorithm=full_crc32 that was introduced in 10.4 and made the default in 10.5 (MDEV-19534) was not fully implemented in the innochecksum tool.

• Apparently, no checksum mismatch will be noticed for page_compressed tables, except for uncompressed pages (such as page 0).
• The page type summary will report all full_crc32 pages as being of "other" type.

In the full_crc32 format, we can validate the page checksum without decrypting or decompressing the page. Therefore, we can (and should) validate all full_crc32 checksums, even if the table is encrypted or compressed.

Note: There is no full_crc32 format for ROW_FORMAT=COMPRESSED tables. They always use an Adler32 checksum or an exclusive OR of two CRC-32C checksums.