Discourage checking hash fields in `object`.

[schwern]

It's glassbox testing to say that an object must contain certain hash fields and should not be encouraged. Unfortunately the object doc example spends half its time on this.

This is particularly egregious with end. This requires that the object contain exactly certain specific fields and no others. And end only applies to certain parts of the object description complicating how the user expects end to work.

To that end...

• [ ] Remove field and end from the object docs.
  • [ ] Leave them working for backwards compat.
• [ ] Allow hash, array, and bag to work inside object.

This eliminates a bunch of redundancy in object with hash and array, and it allows the object docs to focus on blackbox testing.

[exodist]

I am not sure we need to allow hash/array to work inside object, instead we can rely on the 'this' prop provided by meta:

object {
    prop this => hash { ... }; # Check the hash of the object
};

This already works as written today.

[exodist]

#76 would discourage the use of Object { ... } in favor of

st Object => sub {
    stc method => 'expect';
}

fields would essentially be discouraged everywhere, so the problem this ticket mentions would be solved.