[backend/frontend] Threat actor group should not be part-of threat actor individual (#9576)

[SarahBocognano]

Proposed changes

• Restric relation between a group and an individual
• Some UI in details, the goal section was a mess (title not truncated, resulting in a bad UI if long goal name)

Related issues

• Threat actor group should not be part-of threat ctor individual #9576

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.26%. Comparing base (7d55b76) to head (b0ffbe9).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #9649      +/-   ##
==========================================
- Coverage   64.29%   64.26%   -0.03%     
==========================================
  Files         655      655              
  Lines       62933    62909      -24     
  Branches     6964     6965       +1     
==========================================
- Hits        40460    40428      -32     
- Misses      22473    22481       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[labo-flg]

@SarahBocognano there is a bit more to do to solve the issue.

1. The model should be as follow:

TAI -> part of -> TAG
TAI -> cooperates with -> TAG
TAI -> derived from -> TAG
TAI -> related to -> TAG
TAG -> cooperates with -> TAI
TAG -> derived from -> TAI
TAG -> related to -> TAI

2. Default relation: cooperates with (available on both directions)

3. Implement a migration to turn all the relationships that are no longer possible to the generic related-to type.

[labo-flg]

partial solution ; see my comment in the PR.

changes done, need re-review

[aHenryJard]

Suggested change

	// eslint-disable-next-line no-plusplus
	for (let i = 0; i < invalidRelationships.length; i++) {
	for (let i = 0; i < invalidRelationships.length; i+=1) {

the fix is to use i+=1 instead of i++