Rename JwtRepository to AuthRepository

[iamacook]

Summary

This renames the domain JwtRepository (now AuthRepository) as the logic is customised to our auth implementation.

Changes

• Rename JwtRepository and interface to AuthRepository
• Rename JwtAccessTokenPayload to AuthPayload, as well as associated builder
• Rename JwtAccessTokenPayloadSchema to AuthPayload
• Amend associated tests with appropriate naming

[coveralls]

Pull Request Test Coverage Report for Build 8832561602

Details

• 20 of 36 (55.56%) changed or added relevant lines in 8 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.5%) to 91.922%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/domain/auth/entities/tests/auth-payload.entity.ts	0	16	0.0%

Files with Coverage Reduction	New Missed Lines	%
src/routes/transactions/entities/tests/human-description.builder.ts	1	90.0%

Totals
Change from base Build 8829404028:	-0.5%
Covered Lines:	6881
Relevant Lines:	7221

---

💛 - Coveralls

[iamacook]

For future reference: this was originally moved to the routes layer after discussion with @hectorgomezv. However, after review we decided it would be better to remain on the domain layer, just renamed.

There is still a question of whether the JWT datasource is inherently a datasource and (if not) all should be located on the route layer. However, we agreed that this can be iterated on as it is currently easier to follow spread across layers.