Investigate & remove sensitive information from logs
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=350817)
</details>
<!--IssueSummary end-->
See https://gitlab.com/gitlab-org/manage/import/backend/discussion/-/issues/9 for context
Sensitive information should not be included in logs or error messages.
# Proposal
- Define (or find definitions of) sensitive information relevant to import / export
+ E.g. tokens, API keys
- Identify how & where logging occurs during the import / export processes
- Identify how & where errors are presented to users during the import / export processes
- Review the above code to ensure sensitive information is not disclosed
- (If warranted and feasible) create rubocop rules to prevent info disclosure in the future
issue