fix(routes): update user_id retrieval logic

[chimpdev]

This pull request includes changes to the src/lib/express/routes/api/v1/users/[user_id]/storage/index.ts file to improve the handling of request parameters. The main changes involve switching from using query parameters to using route parameters for the user_id.

Changes to request parameter handling:

• Changed the RequestQuery interface to RequestParams to reflect the use of route parameters instead of query parameters. (src/lib/express/routes/api/v1/users/[user_id]/storage/index.tsL10-R10)
• Updated the get route to extract user_id from request.params instead of request.query. (src/lib/express/routes/api/v1/users/[user_id]/storage/index.tsL24-R25)
• Updated the del route to extract user_id from request.params instead of request.query. (src/lib/express/routes/api/v1/users/[user_id]/storage/index.tsL49-R50)

[what-the-diff]

PR Summary

• Interface Renamed for Better Clarity
  The previous RequestQuery interface has now been renamed to RequestParams. This name change will make the interface's purpose clearer, avoiding confusion in its usage.

• Simplified Request Handler Signatures
  We've streamlined our request handler function signatures, by replacing the more complex, unreadable initial type Request<unknown, unknown, unknown, RequestQuery> with a more intuitive and straightforward Request<RequestParams>.

• Improved Extraction Method for User Identification
  The method of extracting the 'user_id' from the request has been revamped. Instead of fetching it from the request.query, we are now retrieving it directly from the request.params. This change has been applied to both the get and del methods, and it should improve the accuracy and performance of our user identification process.