Anonymous types in Environment variables don't type-check

When an object type appears within an `Env` yaml file, the resulting variable reference does not type check unless the `custom_type: <type_name>` metadata tag is set. The rule schema for a template supports anonymous types by way of dynamically assigning type names derived from context. The same should be true for variable and function declarations within an `Env`.