Perform requirements analysis on static argument to use command

[kostmo]

From #1287 (comment):

If you write a program like build {move; use "flerb" forward; move} it will fail, because the requirements analysis will not figure out that we should automatically equip a flerb when building the child robot. You would have to explicitly write e.g. build {move; require "flerb"; use "flerb" forward; move}. We might consider adding something to the requirements analysis which will at least work when use is applied to a statically known device name, as in this example.

[byorgey]

I might do this at some point, but in case someone else wants to tackle it first, it would require adding a special case for TApp (TConst Use) (TText device) to the requirements' function, right before the generic case for TApp:

swarm/src/swarm-lang/Swarm/Language/Requirement.hs

Lines 222 to 225 in 5a034b5

	-- An application simply requires the union of the capabilities
	-- from the left- and right-hand sides. This assumes that the
	-- argument will be used at least once by the function.
	TApp t1 t2 -> go ctx t1 <> go ctx t2

I suppose it should return singletonDev device in that case.