Add Targeted Messaging Datasource

[hectorgomezv]

Summary

This adds a new datasource for the Targeted Messaging feature, consisting of the following persistence entities.

• Outreach: a messaging campaign with name, start date, and end date.
• Targeted Safe: an entity representing a Safe address targeted for a given Outreach.
• Submission: a response to a given Outreach, given by a signer address of the Targeted Safe.

Changes

• Adds a database migration to initialize the tables for each entity.
• Adds a TargetedMessagingDatasource containing methods to interact with Outreaches, Targeted Safes, and Submissions.

[coveralls]

Pull Request Test Coverage Report for Build 11106068331

Details

• 42 of 67 (62.69%) changed or added relevant lines in 8 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.2%) to 90.714%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/domain/targeted-messaging/entities/outreach.entity.ts	0	3	0.0%
src/domain/targeted-messaging/entities/targeted-safe.entity.ts	0	4	0.0%
src/domain/targeted-messaging/entities/create-outreach.dto.entity.ts	0	6	0.0%
src/domain/targeted-messaging/entities/create-targeted-safes.dto.entity.ts	0	6	0.0%
src/domain/targeted-messaging/entities/submission.entity.ts	0	6	0.0%

Files with Coverage Reduction	New Missed Lines	%
src/routes/transactions/mappers/common/transaction-info.mapper.ts	1	54.61%

Totals
Change from base Build 11102081679:	-0.2%
Covered Lines:	8468
Relevant Lines:	8970

---

💛 - Coveralls

[iamacook]

Do you think we should make these camel case for consistency? (I won't mark the others.)

Suggested change

	created_at: outreach.created_at,
	updated_at: outreach.updated_at,
	createdAt: outreach.created_at,
	updatedAt: outreach.updated_at,

[hectorgomezv]

The issue we would have with that is created_at is inherited from RowSchema, which defines those. Maybe at the domain level we could use Partial<> typescript types, and ignore the database-specific date-control fields, but that would require a general refactor. I'd let this as is for now, and re-evaluate the need for those fields after the ORM integration, wdyt?

[iamacook]

I think it's fine as is.