Add support for creating GSD entries from data.gsd.id about gsd-tools

[joshbuker]

Require summary, details, and at least 1 reference. All other fields optional

[joshbuker]

Starting work on this.

[kurtseifried]

At what stage is the GSD ID actually going to be set? We have some options:

1. at the moment of reservation, a GSD entry is created with the ID and modified date, and a PR is linked to it, which once accepted populates the entry
2. at some point after request, e.g. an approval is granted and a GSD entry is created with the ID and modified date, and a PR is linked to it, which once accepted populates the entry
3. after approval, e.g. a request is made, marked as approved, a fully populated GSD entry is created

There are advantages and disadvantages to each way (e.g. supporting reservation at request means people can start using the GSD entry right away, much like they do for reserved CVE ids).

[joshbuker]

The easiest option from the data.gsd.id perspective would be to allow reserving the GSD ID via an API request. Then when you go to create a GSD ID with data.gsd.id, it reserves an ID and immediately uses it to create a PR updating the related json file.

It would make sense for the reservations created this way to mark who requested them (it can provide the GitHub username/UID for this)

[joshbuker]

Moving this from a dialog to a webpage to allow direct linking

https://data.gsd.id/create will be the endpoint once deployed