Create support for static activation context values for event handler methods

This way, we can have more than one event handler in the same class with the same parameters, but different names, and let Tapestry choose the appropriate one instead of having a single event handler method that needs have logic to do different things for different values of activation context values. This can be pretty useful for implementing multiple REST endpoints in the same class in the future.