Hierarchical navigation in organisational units in J2ME client

Description:
Allow users to report for more than one peer org units or own underlying org units by adding hierarchical navigation in the organizational units. This screen will also eventually be reused for viewing reports.

Use Case:
This will affect users assigned to several org units in different levels. From the “Select org unit” screen, user will see the highest level of org units assigned to him. Upon highlighting an org unit, user will have an option to “Select” the org unit or to “View <underlying org unit level>” (e.g. “View districts”). If the user chooses the “Select” option, selected org unit will be set as default org unit for the reports. If the user selects “View <underlying org unit level>”, user will be brought to another “Select org unit” screen listing the selected org unit’s underlying org units. In case user is in the lowest org unit level, the "View <underlying org unit level>" will no longer be displayed.

Technical Implementation:
The OrgUnit class will have an additional Vector attribute of OrgUnit objects for storing the underlying Org Units. This will require changes in the dhis-service-mobile's OrgUnits related classes and the dhis-mobile trunks' OrgUnit model and OrgUnitSelectView.