`cookieToken` in Auth Response Should Reflect Saved Auth Cookie

[UnnikrishnanBhargavakurup]

Currently, the cookieToken in the authentication response object is incorrectly showing the value stored in the Hello configuration object instead of the actual authentication cookie saved in the browser when cookieToken is set to true in the Hello configuration.

Steps to Reproduce:

1. Set cookieToken to true in the Hello configuration.
2. Perform an authentication request.
3. Observe the cookieToken value in the response.

Expected Behavior:

The cookieToken field should display the authentication cookie saved in the browser.

Actual Behavior:

The cookieToken field incorrectly reflects the value from the Hello configuration object.

Example Response Object:

{
    "isLoggedIn": true,
    "cookieToken": null, // Incorrect value; fetched from the config object
    "authCookie": {
        "sub": "sub_duZ19u8PWtdKdNSoj8qpntYb_GNY",
        "iat": 1734599554,
        "name": "Unnikrishnan B",
        "nickname": "unni",
        "email": "my-email@example.com",
        "picture": "https://pictures.hello.coop/r/061f10f3-75ff-4f32-a6f0-1ea113d3cb5c.jpeg",
        "email_verified": true
    }
}

Suggested Fix:

Ensure that the cookieToken field in the authentication response accurately reflects the saved authentication cookie when the cookieToken option in the Hello configuration is enabled.

Additional Context:

This issue may lead to confusion when verifying the cookie-based authentication process.

[UnnikrishnanBhargavakurup]

Fixed in the PR: #13