Use a database instead of a text file for the SEND blocks

Description

We currently write onto a txt file to remember the the size of received blocks, last used date, file hash, block hash and peerId. When we parse the file to delete the oldest blocks, or when we need any information actually, we need to parse the entire file with a regex to do so:

Total: 4780
Size: 956 | Timestamp: 2024-08-26 15:25:43.334027200 UTC | file_hash: 79c29b5bddd0ffa7af86cc4d8a46e9fb6a872faaaf96c3862799101c28bd135e | block_hash: 728f6cdb8727594b8078d279908dbae12929afe26213193efd94efc324a8335 | peer_id: 12D3KooWDpJ7As7BWAwRMfu1VU2WCqNjvq387JEYKDBj4kx6nXTN
Size: 956 | Timestamp: 2024-08-26 15:25:43.339230302 UTC | file_hash: 79c29b5bddd0ffa7af86cc4d8a46e9fb6a872faaaf96c3862799101c28bd135e | block_hash: 79eb3e474912e676e45ac5c31cf3af462f3ecf548dd785c3c237d824c4b54c73 | peer_id: 12D3KooWDpJ7As7BWAwRMfu1VU2WCqNjvq387JEYKDBj4kx6nXTN
Size: 956 | Timestamp: 2024-08-26 15:25:43.353970675 UTC | file_hash: 79c29b5bddd0ffa7af86cc4d8a46e9fb6a872faaaf96c3862799101c28bd135e | block_hash: 4d5ce8440aadd1e6c837ab2897f08b32c761bdd8968e0552363aa6cf85 | peer_id: 12D3KooWDpJ7As7BWAwRMfu1VU2WCqNjvq387JEYKDBj4kx6nXTN
Size: 956 | Timestamp: 2024-08-26 15:25:43.450902060 UTC | file_hash: 79c29b5bddd0ffa7af86cc4d8a46e9fb6a872faaaf96c3862799101c28bd135e | block_hash: 188827661348275e13f35d1c8bb23db2bc176bb933de569d5caaf926d9068 | peer_id: 12D3KooWDpJ7As7BWAwRMfu1VU2WCqNjvq387JEYKDBj4kx6nXTN
Size: 956 | Timestamp: 2024-08-26 15:25:43.473785321 UTC | file_hash: 79c29b5bddd0ffa7af86cc4d8a46e9fb6a872faaaf96c3862799101c28bd135e | block_hash: 6f84b618bb7e8456d7319b0bb9f7ac5871ccb41c8e153eafc8a15ef2f7874c | peer_id: 12D3KooWDpJ7As7BWAwRMfu1VU2WCqNjvq387JEYKDBj4kx6nXTN

This is un-effective and would be more suited for use with a database which would easily allow adding and querying data about blocks received via a SEND request