Order of isRendered and pushComponentToEL prevents rendered="#{}" based on component implicit object

Current specification for lifecycles methods:
1) processDecodes
2) processValidators
3) processUpdates
4) encodeAll
4) encodeBegin

explicitly says that:

1) If the rendered property of this UIComponent is false, skip further processing.
2) call pushComponentToEL

But in that order of invocations it is impossible to achieve rendered like this:

i.e. any rendered ValueEpression based on component itself.
#### Affected Versions
[2.1]

Start by reading the lifecycle method specification described in the issue and reproduce the h:outputText example using a rendered expression based on the component itself. Done means the lifecycle ordering or specification permits the component to be available for that expression without breaking the stated processing rules.

Written by the indexing model from the issue text.