[#2] Configurable success URL for LoginContextService and security.loginForm component
update to T5.4-beta-22
Merge pull request #8 from balapal/task-2

[#2] Configurable success URL for LoginContextService and security.login...
FIXED - #2: Configurable success URL for security.loginForm on per
component render basis 
- remove LoginContextService.getSuccessPage(String successURL). It's
semantically incorrect and unnecessary since the loginContextService
doesn't need to be invoked if you return a user configured success url
- revert changes to Login.java/.tml in
9bd7afe352e05fc2ca23247efced618aac6bc7b7. Passing the success url as a
context parameter makes ugly urls and the author of the pull request
didn't explain why context parameter is in any way preferable to
cookies. Typically, context represents the state and the already
suggested use for the login page state is to convey the state of the
user (unauthenticated, unauthorized, etc.). It's trivial to create a
custom Login page and I expect most users to do so than try to use the
one provided by default
- keep LoginForm's successUrl component parameter and rework the test so
it demonstrates the use case. It's relatively cheap to support and may
have its use cases
Use BASEURI attribute from the superclass
FIXED - #12: The default for SecuritySymbols.SUCCESS_URL should be "${"
+ SymbolConstants.START_PAGE_NAME + "}" 
- implemented as suggested
FIXED - #13: Remove deprecated PageService
Merge remote-tracking branch 'upstream/master' into disable-security-via-symbol
skip Tapestry's built-in services, they won't be annotated anyway