feat(postgres, sqlite): add conflictWhere option to upsert

[wbourne0]

Pull Request check-list

Please make sure to review and check all of these items:

• Does npm run test or npm run test-DIALECT pass with this change (including linting)?
• Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
• Have you added new tests to prevent regressions?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Did you update the typescript typings accordingly (if applicable)?
• Did you follow the commit message conventions explained in CONTRIBUTING.md?

Description of change

• Added the option conflictWhere to QueryGenerator.prototype.insertQuery. This is used to generate the ON CONFLICT WHERE part of the query (note: not ON CONFLICT DO UPDATE WHERE).
• Added an option to Model.upsert, conflictWhere, This is passed to the query generator.
• Updated types
• Added tests

Example use case:

const Memberships = sequelize.define(
  'memberships',
  {
    user_id: { type: DataTypes.INTEGER, allowNull: false },
    foreign_key: { type: DataTypes.INTEGER, allowNull: false },
    permissions: { type: DataTypes.ENUM('admin', 'member', 'guest'), allowNull: false }
  },
  {
    deletedAt: 'time_deleted',
    indexes: [
      {
        fields: ['user_id', 'foreign_key'],
        unique: true,
        where: { time_deleted: null },
      },
    ],
  }
);

// Adds a membership for a user as an admin (updates previous membership instead if there is one)
await Memberships.upsert(
  {
    user_id: userId,
    foreign_id: foreignId,
    permissions: 'admin',
  },
  {
    conflictWhere: { time_deleted: null },
  }
);

Closes #13412.

TODO:

Add some tests which validate conflictWhere & conflictFields work together properly.

made the requested change.

[wbourne0]

Update on this: I ended up implementing this in a fork, but IIRC there was an issue I had w/ it (I believe it was around the logic upsert uses to determine which conflict columns to use, which isn't in the scope of this PR).

I want to verify that it wasn't an issue with this change itself before I merge it.

[sdepold]

@allawesome497 What shall we do with this one?

[wbourne0]

@allawesome497 What shall we do with this one?

I'll need to resolve merge conflicts, but it should be fine.

Now that #13723 is merged I think I'll also add a few more tests which test the combined behavi for some more specific use cases.

[wbourne0]

Bumping this -- what's the status?

Waiting for reviewers atm; just bumped it in the sequelize slack.

requested changes made

[ephys]

I still think we need to do a thorough clean up of the different options upsert accepts but this is good

[wbourne0]

@ephys re-requesting review - had to patch for compatibility with main which dismissed your approval.

[wbourne0]

@WikiRik can you approve this again? the rebase dismissed it.