Mr2011/issue 310/issue match ordering

[MR2011]

Description

This PR adds ordering for IssueMatches for the following attributes:

• PrimaryName
• TargetRemediationDate
• ComponentInstance CCRN

Furthermore, a new cursor implementation has been added. Currently, only IssueMatch uses the new implementation. Instead of investing time to make the current implementation generic, I simply duplicated the relevant code. Once the cursor is used by all entities, this code duplication will be removed.

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

• Closes feat(issueMatch): Ordering and Pagination #310

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help
• Separate ticket for tests # (issue/pr)

Added to documentation?

• 📜 README.md
• 🤝 Documentation pages updated
• 🙅 no documentation needed
• (if applicable) generated OpenAPI docs for CRD changes

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[dorneanu]

I'm missing some documentation about several functions/methods.

[dorneanu]

Muy bien

[drochow]

I'd recommend to move the entity.DbColumnName and the entity.Cursor to the DB layer.