Drop getPreferredShuffleLayout methods from SPI

[arhimondr]

Description

Use getNewTableLayout/getInsertLayout instead as they are expected to be mutually exclusive with getPreferredShuffleLayout*

Motivation and Context

The preferredShuffleLayout SPI was introduced as an experimental one. The optimizer expects either preferredShuffleLayout or getInsertLayout/ getNewTableLayout to return an non empty layout, but not both.

Impact

Some custom connectors may need to apply a migration

Test Plan

CI

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

SPI Changes
* Remove experimental getPreferredShuffleLayout methods from the connector metadata in favor of existing `getNewTableLayout`, `getInsertLayout` methods :pr:`12345`

[prestodb-ci]

Saved that user @arhimondr is from Meta