Add: vCard Version selection for export #344

[jguegel]

Type of change(s)

• Bug fix
• Feature / enhancement
• Infrastructure / tooling (CI, build, deps, tests)
• Documentation

What changed and why

• Added selection for vCard Version, for allowing also sharing contacts with e.g. whatsapp by selecting Version 3.0

Tests performed

• changed setting and tried exports to different IM

Before & after preview

• new Setting "vCard Version"

Closes the following issue(s)

• Closes Sharing a contact with whatsapp does not work #344

Checklist

• I read the contribution guidelines.
• I manually tested my changes on device/emulator (if applicable).
• I updated the "Unreleased" section in CHANGELOG.md (if applicable).
• I have self-reviewed my pull request (no typos, formatting errors, etc.).
• All checks are passing.

[jguegel]

note:
detekt not passing:
VcfExporter.kt:157:17: Function addEvents is nested too deeply. [NestedBlockDepth]
VcfExporter.kt:24:7: Class 'VcfExporter' with '17' functions detected. Defined threshold inside classes is set to '11' [TooManyFunctions]

• please advise how to "simplify" (i actually only added the getVCardVersion function, but detekt wouldn't let me pass)
• also likely using string for version not correct, but couldn't make it work with int

please be patient, just trying to help the community, if too much is wrong just close the PR

[jguegel]

@Tchiller thanks for the feedback, bundling into a new object out has been a good idea. will have a look into it

[jguegel]

@Tchiller please check again, i decided to split up in multiple files to avoid lint complaints

[Tchiller]

Hey @jguegel — went through the post-March state in detail. Most of it's fine, but a few concerns plus one structural one (the Main/Additional split).
Would you be fine if I just send a merge request against your branch with my ideas as commits? You can then cherry pick what you want to have.

[Tchiller]

@naveensingh Quick question on existing behavior: contactsFailed is never incremented (was the case before this PR too), so EXPORT_PARTIAL looks unreachable. Since this code is being reorganized here anyway, it'd be a natural moment to either revive it via per-contact try/catch or drop the partial state entirely. Any preference? Happy to handle in a follow-up PR if you'd rather keep this one focused.