Revisit Options.CheckServerOptionsExist, uncouple it's method

Options.CheckServerOptionsExist seems awkward in it's implementation right now and where we use it, we should revisit this so it doesn't seem like spaghetti code as we check and/or insert option collection records for a guild.

Maybe find a way to auto-populate the table when a bot is invited as well?

Start by locating Options.CheckServerOptionsExist and every place it checks or inserts option collection records for a guild. Then trace the bot-invitation flow to assess whether records can be populated there. Done means the option-checking logic is decoupled from its current callers and the intended record-creation behavior is consistent.

Written by the indexing model from the issue text.