Downstream resoucebundle initializeitems can fail to reload when having reloading upstream resourcebundle initializeitems

Although reloading of ResourceBundle initializeitems will only merge their content without first performing a contentdelete, they are currently checked and possibly marked as upstream items of other (downstream) resourcebundle initializeitems which contentpath(s) are equal to or start with the same contentpath(s).
This then can block execution of such downstream resourcebundle initializeitems if they have a lower or equal (which is a common case!) sequence number and a lower alphabetic name sort order.

However, as such resourcebundle initialize items never perform a contentdelete but only merge their content, there actually is no need to check and possibly mark upstream/downstream dependencies between resourcebundle initialize items!

More specifically, (currently) only contentresource initializeitems do need to check for potential downstream initializeitem dependencies. All other initializeitems only need to be considered as potential downstream item.

Another potential (limited) use-case causing the same problem is that the execution order of initializeitems which do have downstream items is not taking upstream/downstream dependencies into account.
This problem only occurs when a downstream initialize item has the same sequence number and a lower alphabetically sorted name than its upstream item.
This can easily be fixed by sorting such upstream items before downstream items before execution.