Association deletion in CC revision

https://github.com/OAGi/Score/issues/486

1. Allow deleting the association(s) from a revised ACC.

   1. #1 - Remove ASCC/BCC record from DB.
      - Execute the same logic we are currently taking for rev=1. Unlike ACC/ASCCP/BCCP, ASCC/BCC will be permanently removed from DB.
      - A history of this action is stored in Log table.

   2. #2 - Mark as a ‘Deleted’ state.
      - Do we need to keep properties such as ‘guid’ or ‘definition’ for the association deleted by the actions? What if the user often takes ‘Add/Delete’ actions for the same association?
      - Should we preserve the ‘Deleted’ CCs in the new release?

   3. Questions
      - No need to worry about backward-compatibility? What if the developer misses the insert?
      - If there are BIE references (for End-user CCs and Extensions), block the deletion.
      - Uplift

      1. for {a.} logic should be changed. b/c we are using GUID for matching key. but we cannot keep the removed record's GUID.

      2. for {b.} deleted state association is not available in BIE.

2. ‘Move to’ feature (One of refactor features).

   1. to upper-level
      e.g.
      Production Order Line Base. Details
      - Status Line Base. Details (*)
      - Line Base. Details (o)
      - Line Identification Base. Details (o)

   2. to lower-level
      e.g.
      Production Order Line Base. Details (o)
      - Status Line Base. Details (*)
      - Line Base. Details
      - Line Identification Base. Details
      - If there are multiple ACCs that are based on the same target ACC, it cannot be available.
      e.g. Maintenance Order Line Base / Shipment Request Order Line Base / Shop Floor Control Base Line Base ...

   3. Are we allow the move to only {a.} ? if there is only one {b.}, should we allow it?