wally update command

[LPGhatguy]

Two major uses:

wally update

Update all dependencies. This will basically just be the same code as wally install, but without populating the try_to_use map with anything.

This is the same as deleting the package's lockfile and running wally install again.

wally update [package-specs]

This should update specific packages only, leaving the rest alone. We should be able to specify package names or package requirements to update here:

# Update roact. If we have multiple versions of roact at once, try to update them all.
wally update roblox/roact

# Update just Promise 2.x, not any other versions like 3.x
wally update evaera/[email protected]

# Update a few things at once
wally update roblox/rodux evaera/fabric

[u-train]

Should users be able to update any dependencies (meaning transitive dependencies as well), or just ones they specified on the manifest?

I think the former would be better since there are more options. Cases where low-level dependencies not directly used can be a source of bugs and hence needing updates.

[benbrimeyer]

Being able to target transient dependences sounds like a mire of odd behavior since you won't be able to audit if your dependencies are going to behave properly

[magnalite]

Closed by #140