Publishing core from GitHub through web interface

[anlu85]

Summary

Provide a web interface that allows the user to publish a core pointing to a GitHub repository.

Motivation

This feature would simplify the process of publishing a core.

Detailed Description

The web interface should provide a mask where the user can specify a GitHub repository. The user should then be given the possibility to specify a version (by pointing to a release, Tag or commit) or catch the latest version.
If a signature file is available on the repository it should also be published. If several cores are available the user should be able to select the correct one.

Possible Implementation

GitHub repo could be read out via GitHub API.
If not exists, the provider section should be automatically added to the core file. (If it exists, it needs to be validated. Perhaps not allowing a provider section in the .core file on the repo is a suitable solution to simplify things...)
To harmonize the publishing process, the new web interface should trigger the API interfaces for core validating and publishing.
Optional: the SW component handling the logic could be published as stand alone python library.

Tasks

• Create user interface
• Implement logic to parse GitHub repo
• Automatically add provider section to .core file
• Publish core through servers API
• Add documentation to clarify the requirements for a core to be published through this interface.

Acceptance Criteria

A core stored at a GitHub repository can be published to the server using the web interface.

Additional Context

There is a pull request for adding core publishing to FuseSoC CLI: Add cli option to publish to core db. #744