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
Adding new validation rules for orders and drugOrders.
 - Null check for careSetting, encounter, urgency, startDate, action field.
 - Null check for dose, dose units, route, frequency for drugOrders with SIMPLE dosingType
 - Null check for instructions for  drugOrders with FREE_TEXT dosingType
 - Null check for dosing_instructions for drugOrders for any other dosingType.
 - Null check for quantity, quantity units, and number of refills for drugOrders with outpatient careSettings.

Fixed tests failing due to these new validations. Fixed standardTestData.xml to create orders which honour these validations.

Removing voiding of Orders & Obs from patient void handler.
These are automatically voided in RequiredDataAdvice. Had to remove to fix some failing tests.