Mysql onconflict update with renames

[joelsonoda]

Fixes #2707

Problem

When using onConflictUpdate with the mysql dialect, the values inserted were not being referenced correctly.

Solution

• Updated the onConflict tests to use querySchema, schemaMeta and query.
• Update mysql dialect to use values for renamed columns

Notes

Not sure if there is a cleaner way to test the same things using query, querySchema and schemaMeta.

Checklist

• Unit test all changes
• Update README.md if applicable
• Add [WIP] to the pull request title if it's work in progress
• Squash commits that aren't meaningful changes
• Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

[CLAassistant]

All committers have signed the CLA.

[guizmaii]

@joelsonoda is your work ready for review?

[joelsonoda]

@guizmaii , I believe it is, unless I should squash the commit for applying the scalafmtAll first

[joelsonoda]

@guizmaii , I think that the code is ready for review, but I haven't been able to determine why the scala 2.13 async check is timing out.
I can produce the same result locally. I don't believe that this is isolated to my branch.

Do you have any suggestions on how to resolve this issue?

[guizmaii]

Do you have any suggestions on how to resolve this issue?

I'm sorry I don't. Maybe @juliano?

[juliano]

I am not sure, I'm under the impression this is related to the latest scala 2.13 OR to #2633 . I don't have much free time atm, will see if I can find some to have a look

[juliano]

Alright, it looks good to me! @guizmaii can you please double check?

[juliano]

Thank you @joelsonoda!