Consistency for tables in info boxes

[corlick98]

Currently the API is inconsistent with how it presents tables inside !!!info boxes.
Some of them use:

• parameters
• • parameters.value
• • parameters.subtable
• • • parameters.subtable.value

and others use:

• parameters
• • value
• • subtable
• • • value

and others use:
Returns a table of sub-tables

• value

The places that use the first are:
/events

• onObjectCollisionEnter
• onObjectCollisionExit
• onObjectCollisionStay
• onCollisionEnter
• onCollisionExit
• onCollisionStay

/base

• paste
• spawnObject
• spawnObjectData
• spawnObjectJSON

/object

• createButton
• createInput
• editButton
• editInput
• clone
• takeObject
• addDecal
• getDecals
• setDecals

/notes

• addNotebookTab
• editNotebookTab

/physics

• cast

/player/instance

• attachCameraToObject
• getHandTransform
• lookAt
• setHandTransform

/ui

• setAttributes

The places that use the second are:
/objects

• setFogOfWarReveal
• setRotationValues
• setHiddenFrom
• setInvisibleTo
• attachHider
• attachInvisibleHider
• setSnapPoints
• setVectorLines

/musicplayer

• getCurrentAudioClip
• getPlaylist
• setCurrentAudioClip
• setPlaylist

/custom-game-objects

• custom-assetbundle
• custom-board
• custom-deck
• custom-dice
• custom-figurine
• custom-model
• custom-tile
• custom-token

/timer

• create

/ui

• getAttributes
• getCustomAssets
• setCustomAssets
• setXmlTable

Places that use the third are:
/object

• getRotationValues
• getStates

Functions that use other formats include:
/object

• getObjects
• getSnapPoints

I feel a decision should be made to unify these into a single format. The first and second are about equally common so I am not sure which it should be.