Add source and destination branch data to compliance entity

What does this MR do?

Add the source and target branch data to the compliance entity.

Additional notes

This is part one of adding branch details to the Compliance Dashboard.

1. Add source and destination branches to compliance entity backend <- this MR
2. Display source and destination branches in compliance dashboard frontend !37628 (merged)

Screenshots

No visual changes.

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related #216279 (closed)