refactor(breaking): Deprecate sync calls

[braindigitalis]

Deprecate sync calls, from now on they will be auto generated with DPP_DEPRECATED on them advising users to use coro.

This bypasses sync depreciation warnings in the unit tests by using the template directly instead. I don't want to touch this with a ten foot pole right now as this is a whole world of fragile callback hell. This can be addressed in the future maybe, but for now, this isnt directly end user facing code and isnt going to cause anyone any hassle.

Code change checklist

• I have ensured that all methods and functions are fully documented using doxygen style comments.
• My code follows the coding style guide.
• I tested that my change works before raising the PR.
• I have ensured that I did not break any existing API calls.
• I have not built my pull request using AI, a static analysis tool or similar without any human oversight.

[netlify]

✅ Deploy Preview for dpp-dev ready!

Name	Link
🔨 Latest commit	e1b40b2
🔍 Latest deploy log	https://app.netlify.com/sites/dpp-dev/deploys/670d24cd03a1fa0009adb74d
😎 Deploy Preview	https://deploy-preview-1280--dpp-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ruslan-ilesik]

Imho, we should fully remove them when we will be c++20 lib by default. Because coro can directly replace sync calls without blocking and callback hell

[braindigitalis]

Imho, we should fully remove them when we will be c++20 lib by default. Because coro can directly replace sync calls without blocking and callback hell

agreed, that likely still isnt for a long time though...