(PUP-488) Add specs fur future Resource parameter/metaparameter access

This is just adding a little additional spec coverage for the future
parser Resource[foo][attribute] syntax where attribute is either a
parameter or a metaparameter.

From debugging, it appears that the only values being accessed during
evaluation are those set either on the resource directly, or the
'defaults' which have been set in the current or parent scopes on the
Resource's type.  No attempt is made to lookup the type class's defined
parameter defaults.