Utility Network Trace: Programmatic starting points review

[dfeinzimer]

Review the usability and workflow for programatic starting points. Some potential issues:

• The component generates graphics, even for programatic points. If the component is closed, those graphics are left on the map.
• The purpose of the the add new starting points button becomes unclear. See comment here.
• The mapPoint and screenPoint initializer parameters seemingly could also be removed when using programatic starting points.

[dfeinzimer]

• The component generates graphics, even for programatic points. If the component is closed, those graphics are left on the map.

As the user provides the graphics overlay, they are able to call removeAllGraphics when the component is closed.

• The purpose of the the add new starting points button becomes unclear...
• The mapPoint and screenPoint initializer parameters seemingly could also be removed when using programatic starting points.

After checking with Kotlin, the interactive ability to add starting points is always present, even if programatic starting points are used. Thus dropping screenPoint but keeping mapPoint (a Point) aligns us more with Kotlin.