Client and server disagree on oceantree growth stage

Apparently `c_spawn("oceantree_short")` is sufficient to observe this behavior

After some experimenting, the problem seems more that the client defaults to the tall animation regardless of the actual growth stage of the tree.

Alright I think I have a pretty good understanding of the issue now. TLDR, I think this can be fixed by moving the random stage selection to the server instead of the client and by having short/normal/tall oceantree share an animation build/bank.

Now for an explanation.

When we c_spawn("oceantree_short"), the server actually runs the constructor for oceantree_short. However, the client runs the constructor for generic oceantree. The client then selects a random stage, meanwhile the server selects stage 1. With other tree types, the server is doing the random stage selection for a generic tree, and the client gets told by (i believe) the growable component, and the issue doesn't occur there. oceantree constructor does a roll on the *client* in order to set the animations since each growth stage has an independent file.

Back to the oceantree_nut. When the nut grows, this is effectively doing a SpawnPrefab("oceantree_short") on the server, but then this issue happens on the client.

Changed Status to Fixed