Flow Classification Rules: allow actors to be the source node

[davidwatkins73]

Description

Currently only applications may be configured in flow classification rules.
Users have requested that Actor entities should also be allowable in these rules.

Starting points:

• [ ] DDL update flow_classification_rule, migrate application_id to an entity ref (kind/id)
• [ ] Update UI for flow classification rule entry
• [ ] Update any dependent external jobs
• [ ] Update calculator: org.finos.waltz.service.data_flow_decorator.LogicalFlowDecoratorRatingsCalculator

Resourcing

We intend to contribute this feature

[davidwatkins73]

Lightly edited email from SJ:

I am trying to bring increased governance to the use of Actors (i.e. non-applications) within Waltz.

We use Actors in our Waltz data flows to show where data moves between applications and Actors.

As a first stab for Waltz Actors I think we need the following:

• Unique ID
• Name
• Description
• Internal/External to Org flag
• Org Owner

We would then want the additional capability to:

• Use an Actor in the Flow Classification Rules (e.g. to make an Actor a Heritage Data Distributor)
• Get the Actors into ext system (e.g.Collibra) to allow us to create formal Authority Statements with Actors) – may be a bigger development need