fix(db-postgres): long array field table aliases cause error even when dbName is used

[r1tsuu]

Fixes #11975

Previously, this configuration was causing errors in postgres due to long names, even though dbName is used:

{
  slug: 'aliases',
  fields: [
    {
      name: 'thisIsALongFieldNameThatWillCauseAPostgresErrorEvenThoughWeSetAShorterDBName',
      dbName: 'shortname',
      type: 'array',
      fields: [
        {
          name: 'nested_field_1',
          type: 'array',
          dbName: 'short_nested_1',
          fields: [],
        },
        {
          name: 'nested_field_2',
          type: 'text',
        },
      ],
    },
  ],
},

This is because we were generating Drizzle relation name (for arrays) always based on the field path and internally, drizzle uses this name for aliasing. Now, if dbName is present, we use _{dbName} instead for the relation name.

[github-actions]

🚀 This is included in version v3.34.0