Auto-Updating manifest for new version/ meta-manifest

Description of the new feature/enhancement

As I understand Winget, an update of an application causes the need for the community to create a new manifest. As many (probably most) public manifests do only reference official setup files (and are not "silent" re-packages) There should be a way for a more generic definition that does not rely on a quick response of a maintainer (and maybe also the winget team to accept a PR)

Proposed technical implementation details (optional)

Define (in the manifest or in some kind of meta-manifest) where the official information about version (and maybe download url) can be retrieved. This means to provide an url and a location within the file referenced by the url. The location within the file can be defined by several techniques, including StringBetween (define the text before and after the Information), XPath (as most sources will be html files) or RegEx.

The repository server checks for updates every 24h or so and updates the the manifest if changes are detected (checksum, download url, version number).

No files, tests, or entry points are named. Start by reviewing how manifests are currently represented and updated, then determine where a meta-manifest could declare an official version or download source and how StringBetween, XPath, or RegEx extraction would fit. Done would include periodic change detection and manifest updates for version, download URL, or checksum changes.