TRUNK-3882 Custom tag to render errors

(cherry picked from commit be50e0dc73b33272bc01482ec59f1ff3bc6f1acb)
Fixed type in - TRUNK-4173
The API should be able to assign OrderTypes - TRUNK-4302
Add other methods to OrderService for managing Order Types - TRUNK-4289

modify changes according to the comments given in the pull request 791
Follow up to remove logic in retireOrderType, unretireOrderType and renamed the dao method for getting order subtypes to match the one in the service layer - TRUNK-4289
Follow up to clean up code in OrderServiceImpl.getOrderSubtypes to be more intuitive - TRUNK-4289
Added test to ensure that validation passes when editing an existing order frequency   - TRUNK-4192
Reduced the max length for order_type.java_class_name column  - TRUNK-4286
Updated OrderFrequencyValidator to implement spring Validator and added tests to ensure that frequency and order type validators get invoked when their supported types get saved
Follow up to fix failing unit tests
Add isType() method to Order class - TRUNK-4290

Follow up - TRUNK-4290
Renamed OrderService.getOrderSubtypes to getSubtypes
Made follow up to add utility method for testing order type hierarchies - TRUNK-4290
Updated OrderService.saveOrder to auto set the careSetting and orderType fields if they are null but present on the passed OrderContext
Updated OrderService.getActiveOrders to return orders with a future startDate
Renamed OrderUtil.isOrderActive to isActiveOrder and moved it to OrderUtilTest