Draft MSSQL Connector

### Description

As mentioned in the discussion regarding `connectors` (see ([https://github.com/apache/iggy/issues/2753#issuecomment-4750883206](https://github.com/apache/iggy/issues/2753#issuecomment-4750883206)), I can share the source code for a project that has been developed with the goal of capturing changes from a `MSQL` database and push them to `Iggy`. It took the changes, grouped them in case of update, so that these were processed atomically on a different system.

Of course it has to be adapted to comply with the standards of this organization, but a good part can be used.

[https://github.com/lsabi/msql_cdc/](https://github.com/lsabi/msql_cdc/)

In case of doubts, feel free to ask, as at the moment I don't have time to work on the development of a proper, production-ready, connector, so I'm sharing it with the hope that someone has more time than me

### Affected area / component

Connectors

### Proposed solution

_No response_

### Alternatives considered

_No response_

### Contribution

- [X] I'm willing to submit a pull request to implement this feature
`Edit 11/07/2026 I'm working on the source connector`

### Good first issue

- [ ] I think this could be a good first issue for a new contributor

Start by reading the linked msql_cdc source project and the connector discussion in issue #2753 to understand the existing approach. Compare it with Iggy's connector standards and verify that the finished connector captures MSSQL changes, groups updates for atomic processing, and pushes them to Iggy.

Written by the indexing model from the issue text.