Default version locking for embedded components

[mpeterdev]

Summary: should we change the default VM behavior to lock embedded component versions?

This is a follow up to an earlier discussion, please read for context: #9 (comment)

We have the ability to lock embedded components to a specific version, but the default behavior is to display the most recent version of a component if no blockheight is supplied.

We recently encountered a bug on the home view of near.org caused by using a component without locking its version and a recent update to that embedded component creating confusing UI. I think this will likely be a source of a lot of undesirable behavior going forward by putting the onus of version-locking on developers every time they embed a component. Being able to embed a child component in an auto-updating fashion has its use cases, but it being the default affects the stability of UX across BOS.

I am in favor of switching the default behavior of embedded components to be that they are rendered at their latest version at time of the parent component being published as suggested by @evgenykuzyakov

My original idea for block versions is that all children components will be automatically locked based on the height of the parent component

Changing default behavior obviously has large implications to existing components on BOS, and would require significant communication. Now seems like a good time to adopt this change though, since it'll only get harder the longer we wait

@k3y0k3y @ilblackdragon @calebjacob @evgenykuzyakov @thisisjoshford @charleslavon