Removed description edit UI / endpoints and put unified base settings
form in repository settings page.
This form is restricted to repo:owner permission same as before.
The internal model of topics is an array but they are stored/edited as single string where each topics are joined with whitespaces.
Having a dedicated topics table with M:M relationship to the repo seems a bit overkill considering we will have external search indexer anyway.
Signed-off-by: Seongmin Lee git@boltless.me
the backend logic here is perfect, no comments there. i am bit more opinionated about the frontend however. would you mind if i merged this as-is and modified the styling by myself here?
thanks for working on this!