Seed script needs additional parameter, otherwise release artefact are not commited

[joergwa]

The ODK managed .gitignore file always includes the release artefacts, so that they are not commited.

When seeding a new repository, by default release artefacts are not committed to the repository (PRs #1183, #1246).
- Pass the --commit-artefacts option (or -r) to the seeding command to force the release artefacts to be committed.

(https://github.com/INCATools/ontology-development-kit/blob/0faf094969a85b41ab5356e2537d64c98b645c17/CHANGELOG.md?plain=1#L83)

I am not sure, how this actually works and why it is intended, but I experience, that after "update_repo" the release files are again added to the .gitignore file.
May be the additional option at seed time will solve that.

[joergwa]

• If the --commit-artefacts option has not been used at seeding time, the release artefacts can still be manually committed to the repository at a later time, but this will require the --force option to git add.