Give `getattr` an optional parameter `baseline`

Currently, there is a frustrating asymmetry between `setattr` and `getattr`. `setattr` accesses and modifies the "baseline" value of an attribute, while `getattr` returns the PRODUCT of that core value and any applicable multipliers (e.g. LocomotionState, subspecies, abilities, etc). This leads to unintuitive behavior where the value reported by `getattr` is different from the value you just set (see the attached image for an example).

The fact that `getattr` factors in multipliers CAN be helpful in many situations. However, it also makes it much more difficult to do things like reliably store an attribute value to revert back to later, or to debug custom bot commands. In order to preserve backwards compatibility, I suggest adding an OPTIONAL parameter `baseline` to `getattr`. This parameter would ensure that after using `/setattr <attr> <value>`, `/getattr <attr>` would always return <value> REGARDLESS of any confounding multipliers.