feat: upload and download config

[aa956]

something like wget or curl --limit-rate=7M would be nice to have if you mean this.

Also not sure if this is download config feature or separate feature but it would be nice to check if the file is already downloaded? Not sure how to implement or how much shall be checked (e.g. current expected save path vs scan of the entire download directory with hashing) but if I recall correctly now civitdl just redownloads everything in batchfile.

It may be a surprise if batchfile contains some SDXL checkpoints and was (re)started just because of the wrong selection from terminal history :)

Now downloading "Juggernaut XL"...
            - Model ID: 133005
            - Version ID: 240840

 12%|████████▋                                                                  | 823M/7.11G 

[OwenTruong]

Hi, for download and upload config, it just means the user is able to upload and download their configuration file of defaults, alias and sorters from the program as backup. Apologies for not being clear. If it make sense to create a new issue next time, please do create one :)

Also, I have added issue #37 and #38. For rate limit, it shouldn't be too bad to implement that.

I agree that it would be better to not have to re-download if possible.

There are a few ways:

• We could scan a root directory for hashes.
• We could scan a root directory for matching filenames.
• We could add a JSON somewhere that would track what models have been downloaded already at a root directory.

Hashes would be the best solution, with JSON being the worst. If it is possible to download hashes from CivitAI, that would be the best. We probably do not want to create hashes locally as that can be slow on some machines.

(I will implement the above two before v2 merges into master)

[OwenTruong]

Issue moved to #29