fix: cleanup requests to adhere to new tracker API

[flaminic]

List of changes:

• the ouMode parameter is used in our code in for event export, tracked entity export. this does not do anything with the new endpoints and should be replaced by orgUnitMode
• for events exports, the attachment={metadata}.json parameter does not do anything and should be removed
• it is not correct in new tracker to use fomat=json and we should instead append .json / .csv at the end
• links=false is invalid and should be removed
• On Events import / Tracked entities import / Tracked entities export, under Advanced Options > Event ID Scheme selectors should be removed. Requests should be updated to remove references to these parameters
• On Events import / Tracked entities import / Events export / Tracked entities export, under Advanced Options > ID Scheme selectors should include the option "Name". Requests should correspondingly be updated to use Name as appropriate
• We have links to documentation for error codes, but the documentation is wrong, can quickly become out of date. Remove the link.

[dhis2-bot]

🚀 Deployed on https://pr-2176--dhis2-import-export.netlify.app

[tomzemp]

Looks good to me! 🚀

I noticed a remaining reference to ouMode in one of the test URLs. Not sure if that's intentional?

import-export-app/src/utils/helper.test.js

Line 6 in d1d50a8

'https://debug.dhis2.org/dev/api/tracker/trackedEntities.json?ouMode=CAPTURE&format=json&includeDeleted=false&dataElementIdScheme=UID&eventIdScheme=UID&orgUnitIdScheme=UID&idScheme=UID&paging=false&totalPages=false&program=lxAQ7Zs9VYR'

[dhis2-bot]

🎉 This PR is included in version 101.1.23 🎉

The release is available on:

• AppHub release
• GitHub release

Your semantic-release bot 📦🚀