[SPARK-52978][SQL] Make FileFormatWriter customizable via SQL configuration

[zhztheplayer]

What changes were proposed in this pull request?

A change to make the V1 file write API FileFormatWriter.write customizable via a SQL configuration option.

Change summary:

1. Add trait FileFormatWriter;
2. Rename the current FileFormatWriter object to DefaultFileFormatWriter, then make it inherit FileFormatWriter;
3. Provide a SQL option spark.sql.execution.fileFormatWriterClass=... (optional) to allow user set a custom implementation class of FileFormatWriter.
   If spark.sql.execution.fileFormatWriterClass is not present in SQL config, DefaultFileFormatWriter will be used.

Why are the changes needed?

Doing this will:

1. Allow 3rd columnar plugins (by setting this option by default) to specify a columnar v1 writer during plugin initialization;
2. Allow user to specify a customized row-based writer for certain purposes, e.g., performance, specific handling of partitioning, etc.;

Does this PR introduce any user-facing change?

A developer-oriented change:

The calls to FileFormatWriter needs to be changed to DefaultFileFormatWriter as the former becomes a trait.

For example, before:

FileFormatWriter.write(...)

After:

DefaultFileFormatWriter.write(...)

How was this patch tested?

Existing tests. And a new test case in FileFormatWriterSuite.

Was this patch authored or co-authored using generative AI tooling?

No.

[zhztheplayer]

cc @cloud-fan @yaooqinn @dongjoon-hyun Appreciate your thoughts on this.

We had some long-standing issues in Gluten that could be resolved by opening up this API. It will also be helpful for lake support in Gluten as well.

[zhztheplayer]

To ease reviewing:

Git determines this file as a creation. However this is mostly a trivial file move, i.e., mv FileFormatWriter.scala DefaultFileFormatWriter.scala. The content is basically identical.