First-class resource config and service config

[jclark]

Currently resource config and service config are expressed using annotations. It would be better if at least some of these annotations were expressed in the language in a more first-class way. In most cases, the Listener type determines the possible resource and service config, but the use of annotations prevents the type system from describing this relationship.

It's also conceptually wrong: the config is data that is fundamental to the operation of the program and not the sort of thing that should require the use of an annotation. Service and resource config expresses many things that on the client side are not expressed via annotations.

This relates to #329, #559, #519.

[jclark]

The new concept for resource functions deals with HTTP methods and paths in a first-class way, thus eliminating allowing one of the main uses of service and resource config to be dealt with in a first-class way.

#559 allows objects to have fields, which is sufficient to represent service config in a first-class way, although #595 might be needed to make it convenient.

We do not plan to do anything further on this beyond the above points.