Fixes issue 32396: cannot filter grid when it is grouped by a column.

Having a column grouped, if a filter was applied in a grid, it was not
possible to apply it.A js error was thrown:
Uncaught TypeError: this.data.willFetchData is not a function.

The problem was in:"this.data.willFetchData(....))" statement which
incorrectly assumed this.data to be an object and willFetchData a function
within it. This is not true when in this situation where this.data is a
Tree class.

It has been fixed by taking into account this case by checking that "this.data" defines the
function.

Fixes Issue 30147: US Region code are wrong

Codes for region updated as follows:
MI - Michigan
MN - Minnesota

Fixed issue 32151: It wasnt possible configure text referenced cols. properly.

It was not possible to configure the Allow Filtering property in colums that used Text reference.
The problem was in the UIDefinition.removeAttributeFromString.

Here the canSort and canFilter properties were being deleted and that was not correct, because in the case of
the "help" column of the Module window, for example, when the method was invoked, it was only desired to remove
the "canSort" property and not the canFilter.
The method has been changed, now, the passed String argument is the one which will be deleted instead of deleting
canSort or canFilter directly.

related to bug 32375: added test case covering preference's client visibility

fixed bug 32375: preferences incorrectly resolve client visibility

Reimplemented client visibility resolution to correctly handle the case of
2 preference candidates with different client visibility.

related to bug 32375: make preference resolution more consistent

In case of several preferences defined for a given property/attribute, the
result of getting value could be undetermistic.

Solved by sorting by preference's id in these cases.

related to bug 32375: preferences incorrectly resolve client visibility

Small code clean up:
-isHigherPriority renamed to getHighestPriority: by convention is* are boolean
getters which was not the case of this one
-removed unneded brackets in condition which didn't help to make the code more
readable

Fixes issue 32386: Set Final good C product as isquantityvariable in QA client

Fixes bug 32083: Move Service Price Rule menu entry under Pricing Setup menu entry

Fixes Issue 32337:Division by zero error when completing an invoice
associated to a closed order (quantity 0) with a promotion

While calculating promotion if qty ordered is non zero then only
use divide by statement else set values to zero

Related to issue 32364: Code review improvements

Call line.getProductCosts only when line.transaction != null in DocInventory.java.

Fixes Issue 32364:NullPointerException when posting a Physical Inventory
with a line without an associated transaction (not stocked product)

- Avoid insertion of zero quantity products in inventory line having
stocked flag as No.
- Code improvement to handle line with null transaction.

Fixes issue 0032381: missing upload image icon
* Restoring upload icon and erase icon

Fixes issue 32233: Payment In and Payment Out lines are not exported to CSV.

The problem was that export to CSV does not work properly in some subtabs without
link to parent column (e.g.Lines subtab of Payment In/Out). Before, It was used
"tabId" to obtaing data for export to CSV and the value of the "tabId" was sent
in a variable called "tab". The Criteria that is run when it is displayed the tab
uses a property named "tabId" instead of "tab".

The solution for this case (and other related cases) is to adapt the code that
exports to CSV to use the same Criteria run when displaying the tab. Now export
to CSV uses tabId property. Besides it has been refactored some piece of code
related with export data in DataSourceServlet to use "tabId" instead of "tab".

Fixed issue 0032044: Ensure stable ids in docs send from WebPOS to the server (Payment API)

- Set some entities ids related to order loading in Web POS to ensure stable ids