[Refactor] Resolvendo conflitos de merge da branch de correção de build para a dev

[FilipeKevyn]

O que foi feito?

O papel deste PR foi alinhar as correções de build, com as atualizações da dev, mantendo todas as funcionalidades ativas e o projeto buildando.

Issue

• Integrar branch de correção de build com a dev e resolver conflitos #689

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 791d1881-dae8-448a-b5a1-fe681b70fd94

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 615-corrigir-build-do-projeto

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[thalesluiz45]

O PR possui inconsistências com a Dev.

Ao editar um profissional:

JSON parse error: Cannot construct instance of "br.org.apae.api.common.dto.servicearea.request.UpdateServiceAreaDTO"(although at least one Creator exists): no String-argument constructor/factory method to deserialize from String value ('Fisio')

---

Ao salvar um novo paciente:
Data de registro não pode ser no futuro