Include all standard columns with citationkey when exporting to old OpenOffice Calc format

[HoussemNasri]

Fixes #8141

Changes made:

• Replace hardcoding fields to be exported, to a call to FieldFactory.getStandardFieldsWithCitationKey()
• Refactor OOCalcDatabase.java
• Remove redundant comments
• Export 130 fields rather than 34 in the previous implementation

NOTE: I didn't include fields with custom names

I have opened a draft PR because I noticed OpenDocumentRepresentation (used to export OpenDocument spreadsheet), having the same problems as OOCalcDatabase, I wanted to ask if fixing OpenDocumentRepresentation should have its own PR or it's ok to include it in this one.

Screenshot for the exported document in OpenOffice 4.1.11, Windows 11

• Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[calixtus]

Hey, thanks for the pr. I think this fix will be a great improvement! Please note that there is already a major refactor of the oo-interface in our backlog. Please take a look into it, so yours and the other one work fine together.

[Siedlerchr]

@calixtus this is completely unrelated to the other open office integration. This is solely an exporter

[calixtus]

Oh i see, thanks. The oo prefix of the filename mislead me.

[HoussemNasri]

I will handle OpenDocumentRepresentation in another PR since #8141 doesn't mention it, this PR is ready for review

[Siedlerchr]

Codewise looks already good, it would be cool to add a test for it. I think at least for the generated XML it should be possible. Have a look at the Docbook5ExporterTest, it uses the XMlUnit testing framework
Idea would be to add a sample xml representation of the document in the test folder

[HoussemNasri]

Thanks, I'll have a look, although I've never written tests before I'll see how that would go.

[HoussemNasri]

There are 2 XML files in the exported zip, content.xml and meta.xml, should we test both of them or just content.xml, if both then should it be one test case or one for each file.

[Siedlerchr]

content.xml should be enough, if the code comment is still right, then the meta.xml and manifest are just already existing files that are just copied over.

[calixtus]

Looks good to me! Thanks

[Siedlerchr]

lgtm from my side as well. Can you please add a changelog entry as well?

[HoussemNasri]

Thank you, I've added an entry in the Changed section