Add complete plan flag to V2 API

[momo3404]

Changes proposed in this PR:

• Add the complete flag to the V2 API to enable accessing all questions and answers belonging to a plan in the API response.
• Per the V2 API Documentation: "The idea is to have a flag which defaults to false and thereby is compliant with the RDA metadata standard, but can be passed in with a value of true to include the questions and answers of the plan."
• The flag is optional and works with the api/v2/plans and api/v2/plans/[plan_id] endpoints. For example: api/v2/plans/12345?complete=true.
• The schema the flag returns is as follows:

•       "complete_plan": [
            {
              "title": "Question 1",
              "question": "<p>What considerations will you take into account with respect to ethical, legal, or commercial issues?</p>\r\n<p><br>Describe any applicable ethical, legal, or commercial considerations related to your project and data. This includes research involving Indigenous communities and knowledges, human subjects, legal and commercial considerations/agreements, partnerships or data with a high level of risk associated with it.</p>",
              "answer": "<p>test</p>"
            },
            {
              "title": "Question 2",
              "question": "<p>What data will you collect or otherwise bring into your project under this plan?</p>\r\n<p><br>Describe the data that will be collected, generated, and/or acquired.</p>",
              "answer": "<p>test</p>"
            },
          ]
  

• Questions with no answers are not included in the response.

[github-actions]

</tr>

	1 Error
🚫	Please include a CHANGELOG entry. You can find it at [CHANGELOG.md](https://github.com/DMPRoadmap/roadmap/blob/main/CHANGELOG.md).

Generated by 🚫 Danger

[aaronskiba]

Up to you, but this might be a tiny bit easier to read:

if @complete && presenter.complete_plan_data.present?
  json.complete_plan do
    json.array! presenter.complete_plan_data do |item|

[aaronskiba]

Did we end up agreeing on the unique identifier (i.e. q.id) for this?

[momo3404]

I think we agreed that it wasn't possible as is to have a unique identifier for a question that would remain unchanged if the question was edited, and that it was shippable as is.

[aaronskiba]

Sorry, maybe I'm misunderstanding, but it might be possible.
When I create a plan, it has a plan.template associated with it. And that template has several questions associated with it. That template should always be associated with that plan, and those questions should always be associated with that template.
If an admin were to update a template question, a new template would be created. However, no plans with the prior template or prior questions would be affected.

Despite all that, we're running out of time. :P You can leave this to ship as-is for now if you'd like.