refactor(app-headless-cms): set list entries fields using ACO config

[leopuleo]

Changes

With this PR, we are refactoring the way we set the fields while listing entries to present in the list table.

Before:

We include all simple fields: "text", "number", "boolean", "file", "long-text", "ref", "datetime".

Now:

We also include fields coming from ACO columns configs, including complex fields such as object and dynamicZone -> Documentation.

The current table column configurations can stay the same, utilizing the name property as the field identifier. Additionally, we are introducing a new fieldIds property that accepts an array of explicitly defined field IDs. This feature will enable developers to create custom cell renderers based on data from other fields.

In the future:

We can remove the default simple fields. However, this change could disrupt existing customizations, as developers might have created or wish to create custom column renderers using these fields without necessarily displaying them in a visible column. (Documentation).

Example

<ContentEntryListConfig>
    {/* Object field with nested fields */}
    <Browser.Table.Column
        name={"address"}
        header={"Street"}
        cell={<AddressCell />}
        modelIds={["article"]}
    />
    {/* Number field */}
    <Browser.Table.Column 
        name={"order"} 
        header={"Order"} 
        modelIds={["article"]} 
    />
    {/* Multiple fieldIds defined using `fieldIds` property */}
    <Browser.Table.Column
        name={"scheduledDate"}
        header={"Scheduled"}
        modelIds={["article"]}
        fieldIds={["scheduledDate", "published"]}
        cell={<ScheduledCell />}
    />
    {/* Dynamic zone field */}
    <Browser.Table.Column
        name={"hero"}
        header={"Hero"}
        modelIds={["article"]}
        cell={<HeroColumn />}
    />
    {/* Column defined with `name` property as a not existing field */}
    <Browser.Table.Column
        name={"notExistingField"}
        header={"Not Existing Field"}
        modelIds={["article"]}
    />
</ContentEntryListConfig>

How Has This Been Tested?

Manually