api: correct DC_CERTCK_ACCEPT_* values and docs

[r10s]

this PR changes DC_CERTCK_ACCEPT_* to the same values in cffi as rust does. and regards the same values as deprecated afterwards

there is some confusion about what is deprecated and what not, see deltachat/deltachat-android#3408

iOS needs to be adapted as it was following the docs in the CFFI before, same desktop. both need to be graceful on reading and strict on writing.

this PR is considered harmful, so we should not merge that in during 1.48 release, there is no urgency, things are fine (wondering if it isn't even worth the effort, however, having different values and deprecations is a call for trouble in the future ...)

[link2xt]

Still need to run npm run build:core:constants.

[r10s]

Still need to run npm run build:core:constants

did so.

this PR is considered harmful

we should not merge that in during 1.48 release phase, the changed defines may easily break things, iOS and desktop need to accept both of DC_CERTCK_ACCEPT_INVALID_CERTIFICATES and DC_CERTCK_ACCEPT_INVALID_CERTIFICATES2 EDIT: disarmed, see below

[r10s]

k, i disarmed the potentially harmful part of this PR: existing constant stay unchanged, only the missing one is added. this only leads to some weird names :)

if implementation do nothing, things stay as before, and things can be improved without stress, without generating blocking issues.

when this PR is merged, we should file issues on desktop/iOS that only DC_CERTCK_ACCEPT_INVALID must be written and DC_CERTCK_ACCEPT_INVALID as well as DC_CERTCK_ACCEPT_INVALID_CERTIFICATE must be accepted on reading ¹

Footnotes

1. that could have been fixed also by a migration or maybe by not changing the constant in the API beforehand, but now it's like that and probably the easiest way, also as the values are gapless now, which is nice) ↩