App constructor improvements

[glutamate]

• include in the planner (task generation) prompt a list of available plugins
• must be able to edit and add new requirements
• use the progress in the task runner. The various blog posts on the Ralph loop recommend a progress.txt file - how do they use it? use the progress list values in the same way
• in often virtual trigger: keep running tasks until 4 mins have elapsed (if active task running is enabled. so it will run almost continuously till done
• error handling - must be enabled by the user, not enabled by default. The vision is self-healing software - when an error occurs, a task is (automatically?) created to fix the error. the error capture is already done in the view's virtual trigger.
• Feedback. This is for users to enter a feature request (or a bug report that did not result in an error exception) which, with admin approval, becomes a task. There is already an action here https://github.com/saltcorn/copilot/blob/main/app-constructor/feedback-action.js and it may mostly work. But setting this up requires the user to create a table and views for the user feedback. The idea here is that there should be a button for creating the full feedback system at the top of the feedback tab - when clicked, create feedback table, edit form, admin list and edit, approval for admin with a app_constructor_feedback button on the admin list#
• avoid all the page reloads. can we use reload embedded view and the tab does not flicker?
• schema should show existing and planned tables (before implemented) in different colours
• only allow switching to tabs that are useful. For instance, until requirements are fixed and schema is applied, show tasks and task chart as disabled
• move everything to async emit to client updates if dynamic updates are enabled