Fixed behavior of insertOrUpdate on tables with auto_increment option (backport #2785)

[mergify]

This is an automatic backport of pull request #2785 done by Mergify.
Cherry-pick of 8665e0e has failed:

On branch mergify/bp/3.4.x/pr-2785
Your branch is up to date with 'origin/3.4.x'.

You are currently cherry-picking commit 8665e0e1.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   slick/src/main/scala/slick/ast/Symbol.scala

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   slick-testkit/src/main/scala/com/typesafe/slick/testkit/tests/InsertTest.scala
	deleted by them: slick-testkit/src/test/scala/slick/test/lifted/MySQLDMLTest.scala
	both modified:   slick/src/main/scala/slick/jdbc/MySQLProfile.scala

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[nafg]

@MarmaladeSky (or @jkugiya) I guess this needs a human to do...

[jkugiya]

This PR looks quite different from the main code base, what are you trying to do? The intent is not verbalized and is difficult to guess.

[nafg]

@jkugiya the previous PR was on main (3.5.x) but @MarmaladeSky wants it in a 3.4.2 release.

I generated this PR with @mergifyio backport but it clearly didn't work too well

[nafg]

@Mergifyio rebase

[mergify]

rebase

☑️ Nothing to do

• any of:
  • #commits-behind>0 [📌 rebase requirement]
  • #commits>1 [📌 rebase requirement]
  • -linear-history [📌 rebase requirement]
• -closed [📌 rebase requirement]
• -conflict [📌 rebase requirement]
• queue-position=-1 [📌 rebase requirement]

[nafg]

@MarmaladeSky what happened?