Use `ChronicDuration` in a thread-safe way

What does this MR do?

Replace chronic_duration with gitlab_chronic_duration
which makes possible to pass additional params to the .parse and .output,
making its usage thread-safe:
https://gitlab.com/gitlab-org/gitlab-chronic-duration/merge_requests/2

Additionally, get rid of the existing monkey-patch of the chronic_duration, as it is naturally incorporated into gitlab_chronic_duration.

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry for user-facing changes, or community contribution. Check the link for other scenarios.
• [-] Documentation created/updated or follow-up review issue created
• Code review guidelines
• [-] Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Related to #66637 (moved)