Deprecate RouteAlias and replace it with existing Route annotation.

It’s simpler to have only one mechanism to register routes using annotations.

Route implementation can be changed to be used multiple times, instead of using also RouteAlias.

Documentation needs review as well after the issue is completed.

[fluorumlabs]

Speaking of route and route aliases. Consider a user profile view, which can be accessible either via /profile (for current user) or via /user/12345 for some other registered user. That translates to

@Route("profile")
@Route("user/:userId(" + RouteParameterRegex.INT + ")")

Obviously, those routes are not aliases to each other, and using @RouteAlias is semantically incorrect in that example.

[denis-anisimov]

Good point.