"Department" field not handled properly (as part of ORG property)

[Maksym-Kozub]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.5.0

Affected Android/Custom ROM version

Android 15

Affected device model

Motorola Edge 50 Neo

How did you install the app?

GitHub releases

Steps to reproduce the bug

1. Create a contact named X in stock Google Contacts app, with "TestCompanyX" in "Company" field and "TestDepartmentX" in the "Department" field.
2. Export that contact from Fossify Contacts to a VCF file (X.vcf).
3. Create a contact named Y in stock Google Contacts app, with "TestCompanyY" in "Company" field and "TestDepartmentY" in the "Department" field.
4. Export that contact from Google Contacts to a VCF file (Y.vcf).
5. Import Y.vcf into Fossify Contacts.

Expected behavior

X.vcf has "ORG:TestCompanyX;TestDepartmentX" property.
The imported Y contact, when opened in Google Contacts, has "TestDepartmentY" in its "Department" field.

Actual behavior

X.vcf has "ORG:TestCompanyX" property.
The imported Y contact, when opened in Google Contacts, has no "Department" field.

Screenshots/Screen recordings

No response

Additional information

I am not even asking for showing that department in Fossify Contacts' UI; that would be a feature request. However, when Fossify Contacts simply drops some part of the ORG property, it means a violation of the integrity of the respective Android object. It is not just some custom field: structured ORG property, separated by semicolons, has been in RFCs since at least 1998 (when RFC 2426 was created), and all its components should be at least silently preserved.