[User Story] Enhanced user experience with extended prerequisite, marketplace and webportal

Motivation

We extend prerequisite field of OpenPAI protocol in #5145 and enable it as one of the minimal sharable unit (unlike runtime plugin, which is mainly backend for cluster admin). With the extended prerequisite, users could have better experience on dataset management, debuggability, checkpoints saving and so on (see examples).

To make better use of the powerful feature, we need marketplace and webportal pages to be updated accordingly. This issue is to propose a complete user story for feature discussion.

How user benefits

With the new feature,

• Admin (and users) could predefine important components (e.g. storage, dataset, failure handling and debugging functions) as prerequisites and share them in marketplace.
  • User could share a prerequisite from existing job, star it (?) or add it to favorite.
• When submitting a job, user could access the prerequisites in job-submission page. By checking (or unchecking) on a drop list, user could include (or excluding) a prerequisite to this job. The job config yaml would be udpated accordingly.
  • Since we support require in the extended prerequisite, the requirements would be checked automatically. For example, user checks a prerequisite for dataset will also include its required storage and essential packages (e.g. mounting utils)
  • To avoid too many prerequisite items slows the page, marketplace would provide the capacity of filtering (e.g. only favorite or recently used)

Start by reading the extended prerequisite proposal in issue #5145 and reviewing the marketplace, webportal, and job-submission pages. Map how prerequisites are shared, filtered, selected, and represented in the job config YAML. Done means the user flow and required page changes are defined for prerequisite sharing, favorites, filtering, selection, and automatic requirements handling.