[PAG-2696] Add prompt attribute to widget xml

[MendixDanijel]

Checklist

• Contains unit tests ❌
• Contains breaking changes ❌
• Compatible with: MX 11
• Did you update version and changelog? ❌
• PR title properly formatted ([XX-000]: description)? ✅

This PR contains

• Bug fix
• Feature
• Refactor
• Documentation
• Other (describe)

What is the purpose of this PR?

Adding prompt attribute to xml file and to widget generator questions.

Relevant changes

• Added optional "prompt" question during setup which is going to be used on widget level.
• Added "prompt" attributes to widget level and to properties level to all xml templates.

What should be covered while testing?

Generating a widget using the bin.js script.

[weirdwater]

Hi @MendixDanijel, thanks for the PR. In my opinion the generated widget should act as a minimal viable widget that can be used immediately in Studio Pro and can be easily adapted to your usecase.

In this case I think the generated prompts act too much as placeholders and should serve more as example prompts. The developer can easily remove them or adapt them to their usecase as needed. Generally after generating the widget the first step is to edit the xml file anyway, so this is a reasonable expectation.

My suggestions would be to:

• Remove the generation prompt. I think it is okay to always generate the example prompts. There are already a lot of questions and the elements are easily removed if not needed.
• Rewrite the prompt elements (including that for the widget) to make sense in the context of the example widgets. Currently they resemble placeholders rather than examples. This is an opportunity to show what kind of prompts we expect and how the prompt element differs from the caption and or description elements.