refactor: use **kwargs instead of very long function declarations

[pmrowla]

should we start using **kwargs @pmrowla @efiop ? it seems we have to change a lot of method just to pass one arguments, and it's not very scalable - not ideal to have functions with 9 args?

Originally posted by @shcheklein in #3600

Any commands and functions that use remote status (i.e. push/pull/fetch/gc/status) require passing 9+ args through multiple function calls in repo/cloud/remote/etc. Would be much cleaner to just use **kwargs and document the expected parameters at the top level function declarations (most of these functions do not currently have docstrings).

[efiop]

Closing as stale