Seeding process should not default to commit release artefacts

[gouttegd]

… or there should at least be an option to disable this.

When a new ODK-managed repository is seeded, all release artefacts from the “initial release“ in the top-level directory are forcefully committed to the repository.

So, even if a project takes the (sensible) decision that they do no want to commit their release artefacts, they will still end up with a "first release" commit in their history in which all the release files are in fact committed.

This behaviour should be configurable, and I’d argue that the default should be not to commit the release artefacts.

[matentzn]

agreed