This follows on from the work carried out in #836
I've added a select box in the Knots settings page which pulls in the users knots and also adds in knot1.tangled.sh. When the user selects one of these options, it will save to their profile in the database. NOTE: I haven't yet implemented adding that to the AT record because I'm not sure on how the lexicon setup works yet!
Then when users go to create a new repo / fork, if there is a value in their profile for the default knot, then that will pre select the knot to use for the new repo / fork.
This is a duplicate of https://tangled.org/tangled.org/core/pulls/858/ which had to be closed because there were merge conflicts which couldn't be resolved due to the origin fork being deleted ๐
sorry for the late review! on the whole the code looks good. my only nit is with the model: we are storing the default knot as a string, but knot deletions can make this go out of sync. i think an FK relationship with the knot registrations table could fix this. we just unset defaults when a knot is deleted.