Resizes TUI elements relative to terminal size.

Addresses #8

This does make some changes to the ratio of the element sizes within the UI, so it won't be a 1:1 match to the previous UI. The most noticeable change is that the TUI now takes up all of the height in the terminal. Let me know if there should be a maximum height/width set instead of always being "fullscreen".

For some reason, when I try to look up my own username, I receive the error message Something went wrong while executing your query. I can look up other users, though. I did some digging, and it appears to be happening in SetupProfileStats.

Press Generate new token and select repo, admin:org, user

Does octotui really need full permissions for repositories, organizations, and user data? That seems like more permissions than necessary. What are the minimum token permissions necessary to use octotui?

This adds a config value in a file called default_owner. The config value is in the format name:type, where name is the user or organization, and type is either user or org. octotui will attempt to read from this config file if the search subcommand is not used. If the config value is not set, then the user is instructed to either fill in this config value or use the search subcommand.

Some other changes this PR makes:

• Refactors code so that most of the logic from LoadToken is moved into a more generic function loadConfigFile
• Fixes bug where octotui would fail early if the config folder exists, but not the config file
• Made renderUser and renderOrganization public functions

Resolves #5

This PR adds a command that allows a user to use the git remote URL to get the GitHub username to search. This should save some typing if they want to look up the user stats of an owner of a repo they're working on.

Some example uses:

• octotui by-remote: search the username from the origin URL
• octotui by-remote --remote upstream: search the username from the upstream URL
• octotui by-remote --repo ../other-project: search the username from the origin URL in a different local repository

This is just a small code refactor for how subcommands are added. Per cobra's documentation, subcommands should be added via the init function. This slightly simplifies the code by not requiring AddCommands to be run in main.

Its a little annoying, but is it possible for the little modules/boxes to adjust to the terminal width instead of being cut off. Also, it would be really cool to be able to modify which modules/boxes show.

I think it would be useful to optionally allow a default user to be set, which can be displayed by simply running octotui with no subcommand. I'm thinking of tools like neofetch and onefetch, which users run to gather information about themselves. The simplest usage for these tools is to run with no additional commands/arguments.

I think this could be stored in a config file like ~/.config/octotui/default-user. If the file is empty, and no arguments are passed, then the user is instructed to either put something in the file, or use octotui search. If the file is not empty, then octotui will automatically use the username in that file unless search is used.