ci: prefix CI check names to avoid BHoMBot collision

[sakanni]

Renames the CI job keys to a ci- prefix so their status-check contexts no longer collide with BHoMBot. When both post the same context name, only the first wins the slot and BHoMBot is suppressed, leaving the BHoMBot-pinned required checks unsatisfied and blocking merges. The ci- prefix lets BHoMBot resume its bare-named checks with no branch-protection change. Source change: BuroHappoldEngineeringAdmin/CI_Toolkit#124.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[sakanni]

@BHoMBot check required

[bhombot-ci]

@sakanni to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check core
• check null-handling
• check serialisation
• check versioning
• check installer

There are 242 requests in the queue ahead of you.

[bhombot-ci]

@sakanni just to let you know, I have provided a check-installer result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @sakanni on SQLite_Toolkit

[bhombot-ci]

@sakanni just to let you know, I have provided a check-installer result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @sakanni on BHoMAnalytics_Toolkit

[bhombot-ci]

@sakanni just to let you know, I have provided a check-installer result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @sakanni on SQL_Toolkit

[bhombot-ci]

The check installer has already been run previously and recorded as a successful check. This check has not been run again at this time.

[adecler]

ci prefix correctly added to all jobs

[bhombot-ci]

@sakanni just to let you know, I have provided a check-ready-to-merge result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @sakanni on SQL_Toolkit