Show "waiting" symbol / disable controls during certain operations

[fedarko]

• During layout
• During expected-to-be-intensive coloring / drawing operations? (coloring can take a while #132)
• During animations (Interaction bugs between animation and sample / feature metadata coloring #195)

Brought up by @antgonza in #375:

When changing layouts it would be good to change the cursor to a waiting/processing pointer and ignore all interactions as a user (me) can continue clicking and changing layouts until the browser brakes

I think it would make sense to have a minimum tree size where this starts being triggered -- for small trees these precautions (or at least the waiting symbol) won't be necessary, but once we get up to say > 100k tips it may be worth adding this stuff in.

It would probably be best to set up reusable functions to enable / disable stuff, similarly to how parts of #319 work. This problem also came up during MetagenomeScope's development; I wound up using smooth transitions between the enabling/disabling operations there, since they were happening so quickly for small datasets I was worried it was gonna be a photosensitivity problem.

[fedarko]

The idea of "disable controls" came up today, where e.g. it's possible to click on the canvas a bunch of times which (unknowingly) triggers a bunch of searches throughout the tree for the closest node. As part of this issue, it'd be good to (while searching is happening) disable the canvas events, or at least the clicking ones.