[Feature] Basic transaction system and endpoints

[DeadlyFirex]

Description Automatize the transaction_log table implemented in prior versions, This is the main feature the microservice should support, this is it's first implementation. Allow users and administrators to track the changes they have made to their balance. Furthermore, add endpoints to leverage this table to users and administrators.

Context As of right now, similar to the audit_log prior versions have implemented the tables, but lack the endpoints to provide and interact with the tables.

Expected Behavior

• Design functions and methods to simplify balance tracking.
• Integrate functionality with the audit_log.
• Create endpoints to interact with this data, for users, and administrators.
• Implement validation of transactions, and of the related request data.

Use Case Examples

• Administrators should be able to view and edit all transactions in the table.
• Users should be able view all transactions of their own, and create new transactions of their own, but not edit history.
• Users and administrators should be able to leverage a simple categorization endpoint, that summarizes gains by category.
• This can be done system-wide for admins, user-scoped for users.

Requirements

• [ ] Research implementation
• [ ] Optionally extend on configuration
• [ ] Create functions and methods to simplify creation
• [ ] Design and implement user endpoints
• [ ] Design and implement administrator endpoints
• [ ] Create summary endpoints
• [ ] Testing and verification
• [ ] Integration into deployment

Considerations

• Optional: create extended configuration fields to manage this function

Additional Information N/A

Dependencies

• Depends-on: #4
• Depends-on: #7

Related

• Depends-on: #4
• Depends-on: #7