datastore_upsert, datastore_create error fixes

[wardi]

Fixes #7683

Proposed fixes:

report postgres record errors consistently against records parameter

datastore_upsert method=insert: prevent 500 on invalid data datastore_create
datastore_create: invalid data errors now reported against records value (not "message")

Features:

• includes tests covering changes
• includes updated documentation
• includes user-visible changes
• includes API changes
• includes bugfix for possible backport

[wardi]

@smotornyuk not sure what's going on with the type check, there's no "cast" at the line in the error and it wasn't failing one commit ago

[smotornyuk]

The master branch is fixed. The issue was caused by two PRs with conflicting changes(one removes the cast import because it's not used inside a module, and another calls cast) which were merged approximately at the same time.

I suspect now you need to merge the master into the current branch because GH action does not see changes from the master if I re-run the type-check job manually from the GitHub interface.

[wardi]

@smotornyuk well, we're getting a different error now. That counts as progress right? 😄

[smotornyuk]

Another PR, but this time it was created 5 months ago and it passed type-check. Since then we've updated dependencies, which slightly change the type signature of the version parser. And because of this after the merge(which was completely legit, as all checks were green) we've got a problem. The only way to avoid such a problem is to review and merge everything immediately:)

I merged the master into the current branch and now it's green, so I won't test my luck and merge this PR