Remove script because instead fix skins during the upgrade, it should be fixed and commited correctly in bt5

This makes tests independent and improve failures detection.

* Fix the issue that Sale Packing List wrongly has Root Applied Rule sometimes when it is created by Delivery Builder with a site which has many activity nodes.

Use helper function to test given encoding

Also, allow to check the transition message after the dialog to make sure, and
retry if the check fails and the maximum number of attempts is not 1.

This way, it is possible to confirm an object and check that it has been
confirmed in only one call including retries.

This patch will always perform conversion against given encoding, in order to check if this codec is valid or not.

Check that declared encoding is supported by python before using it.

There is no reason not to support sql_catalog_raise_error_on_uid_check for both cases of UID inconsistency. UID change happens for example with inconsistent catalog and ZODB after disaster recovery. It can be useful to prevent raise during a double catalogin of the database after a disaster recovery. Else, it is just impossible to recover.

add new field for new coordinate_text property
improve proxyfication (from deprecated field library)

thanks to css class horizontal_align_form_box, sub fields will be displayed horizontally

increment version for 22baeab9c43113428ccf9472798732dc212d305f

Detailed properties take precedence on coordinate_text (raw string) if at least one of them is defined.
Introduce isDetailed method in coordinate API, which return True if at least one detailed property is defined.

Acquire more properties from coordinates

raw input is available with getData.
Backward compatibility is supported.

Associate it to all Coordinate Classes.
It defines data property to hold user input value

fromText was used to parse and store in different placeholders slices of coordinate strings.
This assumption is wrong. Parsing will be dedicated to asText renderer.