[DEA] Add support to input values for question group - repeatable and non-repeatable

[mahalakshme]

Need:

Sometimes admins want to edit some data entered by other users. And since admins are using master catchment, using mobile app to do the same via sync will be more time consuming. Hence they prefer to do it via DEA. Currently this is not possible for organisations whose forms use question group(repeatable or non-repeatable) since currently DEA doesn't support input for question group concepts(repeatable or non-repeatable).

Acceptance criteria:

• Being able to take input for concepts within question group(QG).
• For RQG, Ability to add more groups using + add button.
• For RQG, Ability to remove groups using the - button.
• For RQG, When the 'Disable addition or removal' is enabled, + and - buttons should not be displayed.
• Being able to edit for all the above scenarios
• In Summary and Recommendations page as well, observations need to display page wise supporting RQG. The UI design part, will already be done as part of this card. I think we just need to use the same component to display observations here if not done.

Mockups:

1. In mobile app currently, we are changing the UI based on the data types of the form elements within the question group. Lets say them as Linear type and Box type. Unlike two different ways in mobile app, in DEA we can just have one way - linear type without using the box type considering webapp will be used on a larger display.

Linear type when coded data type present:

Box type when coded data type not present:

2. For RQG, Video and mockups regarding when to enable and disable + and - buttons. Also note that we need to display the question group concept name.
   Video link: https://github.com/avniproject/avni-webapp/assets/10369963/adb96697-f886-412b-947e-f98077bc175a
   

3. For RQG, When 'manual addition and removal' disabled, + and - icons should not be displayed like in the mobile:

4. Also For question group which is not repeatable, + and - icons should not be displayed like in mobile:
   

5. Summary and Recommendations page current reality(left) Vs expectation(mobile)
   

Out of scope:

• Form element, form element group rules, decision rule and visit schedule rules(currently supported in DEA) need to execute as expected on form elements within RQG and QG
• Supporting subject concept type within RQG

Suggestions:

• we can potentially move decision and visit schedule rules as a different card
• subject support - sync concept values - confirm - based on minor/major - validation
• sync concept value - drop down/radio group - webapp?
• can be supported - DEA complementary to mobile

[petmongrels]

• For testing, it may be better to wait for the rules stories to complete as well - since they are not working correctly. I tested by disabling FormElementStatus rules. Without rules working doing QA on existing implementations may be misleading.

[mahalakshme]

@petmongrels @AchalaBelokar just mentioning whatever discussed in standup:

• I am creating cards adhering to INVEST principles, such that every card can be independently tested. From that perspective, @AchalaBelokar you can make sure cases around the ACs mentioned, works as expected. I am also hoping you are aware where what rules are employed. So I don't think testing this card should be a problem.