Allow updating/uploading asset using Open Cloud API key

[ryanlua]

Currently, asset uploading only supports using a cookie (--cookie <COOKIE>) and not Open Cloud API Keys, although it is technically possible (in my GitHub Action, it uses an Open Cloud API key to update a Roblox model).

$ rojo upload --api_key "<API_KEY>" --asset_id 13121004608
[ERROR rojo] --universe_id must be provided to use the Open Cloud API

Support for API keys should be added/fixed since API keys have an explicit asset:read permission, which makes them work great with this command, especially in CI scenarios.

Related #504 #486

[ryanlua]

Could I be assigned this issue?

It should be simple enough to knock out, and I already have experience through my GitHub Action with using Open Cloud. Patch whatever should be uploaded to https://apis.roblox.com/assets/v1/assets/{assetId} in accordance with the Open Cloud API.

We don't need to worry if the asset is new, since the command requires an asset ID and has no flags for changing things such as metadata. Being able to update metadata, such as the asset display name and description, is definitely next for this command.

[ryanlua]

Some random thing, looking through its implementation, we can probably use Rojo here instead of Lune to upload the plugin to the CI when the command is fixed.

rojo/.github/workflows/release.yml

Line 53 in 9bbb1ed

run: lune run upload-plugin Rojo.rbxm

[Dekkonot]

You're more than welcome to add support for uploading to non-places using Open Cloud, but last time I checked Roblox still does not support uploading plugins via Open Cloud, so we will need to continue supporting cookies. It is annoying but it's also simply how it is.