Move gitsign under tooling section

[Hayden-IO]

          gitsign is a unique case, it's more like Cosign in that it's a tool built on top of an SDK to sign a specific format (commits, rather than containers/blobs like Cosign).

What do you think about an additional section for Sigstore tooling that is not Cosign? Something like:

• Cosign
  • Sign
  • Verify
  • Etc
• Client libraries
  • sigstore-python
  • sigstore-java
  • etc
• Sigstore tools
  • gitsign
  • model signing (https://github.com/sigstore/model-transparency)
  • In the future, more tools

If we were to ever refactor Cosign to be smaller in scope to only support container signing, it would then just move under Sigstore tooling, though I don't expect that to happen. But it would give us a category to expand over time as more use cases for Sigstore signing arise.

Originally posted by @haydentherapper in #323 (comment)

[Hayden-IO]

cc @hayleycd

Also cc @mihaimaruseac, who could help with some model signing docs

[mihaimaruseac]

We're currently working on documenting the model signing repo and can definitely export these here too once we're done

[Hayden-IO]

@mihaimaruseac What we've done with the clients is not to require documentation live in this repo, but to have a brief outline of the purpose of the client, a quickstart guide that shouldn't be hard to keep up to date, and a pointer back to the original repo. See https://docs.sigstore.dev/language_clients/language_client_overview/ for an example.

I think we should do the same with model signing.

[mihaimaruseac]

Oh, that's even simpler then. Thanks for the pointer