Feature refactor question entity

[idelcano]

📌 References

• Issue: close Refactor: Question domain entity should not has option list because option domain entity is a aggregate root also #2318
• Related pull-requests:

🎩 What is the goal?

Remove option list from question.

📝 How is it being implemented?

The ereferrals api pull obtains an object with the list of questions and its options within each question.

To convert and save it i used a object called "Metadata" as wrapper of question and question option relation. And I did change the pull of Questions to pull of Metadata (with separated question and options with the question code as hashmap id in the case of the options).

In that process i needed change the order and way to save some data.

I needed replace the Question.hasOptions() method by a OptionLocalDataSource Query

I found (and fix) some bugs with the optionattributes( not correct colour value and not saved in database).

I moved "IMetadataConfigurationDataSource" file from main to ereferrals.

💥 How can it be tested?

Use case 1: Test cnm pull (login on settings, HC, and send a survey), and the load of village question
Use case 2: Test Ereferrals pull. Send a survey.
Use case 2: Run ereferrals tests (remember move to ereferrals staging variant"

Note: in the case of ereferrals i compare the databases too to see if the result is correct with the user 8001.

💾 Requires DB migration?

• Nope, we can just merge this branch.
• Yes, but we need to apply it before merging this branch.
• Yes, it's already applied.

🎨 UI changes?

• Nope, the UI remains as beautiful as it was before!
• Yeap, here you have some screenshots-