Port UI5PathGraph to use the newer data flow API

[jeongsoolee09]

What This PR Contributes

Port over UI5PathGraph and all UI5 queries depending on it

Port UI5 queries from the old data flow API that uses TaintTracking::Configuration to the new one. Porting UI5 queries requires care since it depends on UI5PathGraph that enables UI5 binding paths appearing in UI5 views (e.g. XML views) to be included in the path information.

The implementation of UI5PathGraph previously depended upon the fact that there is only one PathNode type: DataFlow::PathNode. This is no longer the case with the newer API where each data flow configuration module has their own PathNode types. Therefore, the new UI5PathGraph is parameterized on a data flow configuration module like the following:

module UI5PathGraph<DataFlow::PathNodeSig ConfigPathNode, DataFlow::PathGraphSig<ConfigPathNode> ConfigPathGraph> {
  ...
}

One could argue that it could be shortened to module UI5PathGraph<DataFlow::GlobalFlowSig ConfigModule> based on the usage module UI5XssUI5PathGraph = UI5PathGraph<UI5XssFlow::PathNode, UI5XssFlow::PathGraph>, but ConfigModule::PathNode does not expose getNode since there is no type-level constraint on the member PathNode (its declaration is only class PathNode;).

Resolve deprecation warning on AmdModuleDefinition.getDependency/1

Use AmdModuleDefinition.getDependencyExpr/1 instead because of the above being deprecated.

Future Works

• Write a developer's guideline on using the new UI5PathGraph, as it is easy to forget to import the instantiated UI5PathGraph.
• Resolve the deprecation warning on PathString.

[knewbury01]

other than a few small questions/nitpicks, this looks good to me!

one more last little request/suggestion - maybe we can also open an issue for the future works item: Write a developer's guideline on using the new UI5PathGraph, as it is easy to forget to import the instantiated UI5PathGraph.

[jeongsoolee09]

@knewbury01 Issue opened at #229!

[knewbury01]

lgtm! thanks for addressing the comments :)