Update some internal testing code which validates whether the DB-based properties are aligned with the file-based properties. This aligns the test with the current/proper semantics.
Update some internal testing code which validates whether the DB-based
properties are aligned with the file-based properties. This aligns the
test with the current/proper semantics.

However, during a "revert" operation, there is an unstable intermediate
state where the WORKING_NODE table still contains a row (with incorrect
properties) which is then used to reinstall the working file. Thus,
enabling TEST_DB_PROPS will cause a failure.

Since this appears to advance correctness, and there are other parts of
our code definitely wrong... I'm committing it.

* subversion/libsvn_wc/props.c:
  (svn_wc__load_props): the return value from read_pristine_props() will
    always be non-NULL, so just immediately do a comparison against the
    fetched base props. if there are no base props, then assert that the
    pristine props are empty. do a similar compare for the working (aka
    ACTUAL) props.
  (svn_wc__load_revert_props): the base_get_props should always return
    non-NULL, and these should always match the revert props.


git-svn-id: f8a4e5e023278da1e04e203c7fe051e3c4285d88@925106 13f79535-47bb-0310-9956-ffa450edef68

wbond/subversion,YueLinHo/Subversion,YueLinHo/Subversion,YueLinHo/Subversion,wbond/subversion,YueLinHo/Subversion,YueLinHo/Subversion,wbond/subversion,YueLinHo/Subversion,wbond/subversion,wbond/subversion,YueLinHo/Subversion,wbond/subversion,wbond/subversion,YueLinHo/Subversion