Clarify that $selected Actions/Functions are included in [project-list] within a ContextUrl

The purpose of putting the project list in the context url is so that the client (i.e., a JSON parser) can differentiate between content that was omitted from a response because they weren't selected versus omitted because they weren't applicable (i.e., dynamic properties, functions and actions)

We support the project-list for properties but we don't specify whether or not it includes actions/functions that are explicitly requested by the client.

In general, the client knows that it can always try to invoke a bound action/function to an entity of the correct type, so it doesn't need to be advertised in the payload, but if a client explicitly selects a function/action then it must be included, if applicable, and the client knows that it's absence means that it is not applicable (can't be called) on the current entity.

This all works fine; we just failed to mention in [Protocol] and [ABNF] that functions/actions from the $select also appear in the project-list