feat(api): add user endpoints

[nganphan123]

Welcome to PrivacyPal! 👋

Fixes: #85
Depends on #129

Description of the change:

Add user data endpoints for fetch and update data from postgres

GET /api/users?id=1
Response:
{
    "result": {
        "data": [
            {
                "id": 1,
                "username": "jane",
                "email": "jdoe@gmail.com",
                "firstname": "jane",
                "lastname": "doe"
            }
        ]
    }
}

GET /api/users
Response:
{
    "result": {
        "data": [
            {
                "id": 1,
                "username": "jane",
                "email": "jdoe@gmail.com",
                "firstname": "jane",
                "lastname": "doe"
            },
            {
                "id": 2,
                "username": "john",
                "email": "jhdoe@gmail.com",
                "firstname": "john",
                "lastname": "doe"
            }
        ]
    }
}

PUT /api/users?id=1
Request:
{
    "firstname": "john",
    "username": "john",
    "email": "jhdoe@gmail.com",
    "lastname": "doe"
}
Response:
{
    "id": 2,
    "username": "john",
    "email": "jhdoe@gmail.com",
    "firstname": "john",
    "lastname": "doe"
}

How to test

1. Run postgres and add some mock data
2. Disable middleware redirect
3. Test each endpoint with Postman or other softwares
4. Test if the apis handle error cases

[github-actions]

This PR/issue depends on:

• feat(db): database schema updates #129
  By Dependent Issues (🤖). Happy coding!

[MyStackOverflows]

this all looks good to me, wondering why it's still 'blocked' by #129? i thought #129 was merged

[tthvo]

this all looks good to me, wondering why it's still 'blocked' by #129? i thought #129 was merged

This PR needs rebasing before the block can be removed. @nganphan123 rebase pls.