chore: Update and Refactor Flask Application and Update Database Configuration

[Dovineowuor]

---

Refactor Flask Application and Update Database Configuration

Description: This pull request includes several key updates and refactoring changes aimed at improving the codebase's readability, security, and maintainability. The changes are detailed below:

Commits:

1. Refactor Flask Application and Update Database Configuration:

   • Improved modularization of the Flask application for better code organization and readability.
   • Enhanced error handling in database operations to prevent application crashes and ensure data integrity.
   • Updated logging for better traceability and debugging support.
   • Improved security by utilizing Flask's URL generation and avoiding manual URL construction.
   • Optimized logic to remove redundant conditions and improve performance.

   Commit ID: 6c83419, 058745e

2. Update Footer Link to Privacy Policy:

   • Updated the footer link to the Privacy Policy in static/footer-copy.html to ensure it points to the correct URL.

   Commit ID: 43deca2

3. Refactor HTML Structure and Update Page Title:

   • Refactored the HTML structure to enhance semantic layout and ensure compliance with modern web standards.
   • Updated page titles for better SEO and user understanding.

   Commit ID: ac7e876

Testing:

• All changes have been tested locally to ensure functionality and integration with the existing codebase.
• Confirmed that all links, especially the updated Privacy Policy link, are correctly navigable.

Notes:

• This refactor prepares the codebase for future enhancements and makes it easier for developers to add new features.
• Ensure that the updated database configuration is compatible with your current deployment environment.

Reviewer Instructions:

• Review the changes in the Flask application and verify the modularization improvements.
• Check the updated footer link in static/footer-copy.html for correctness.
• Test the HTML structure changes to ensure no layout issues are introduced.

Screenshots: (if applicable)

• Include before and after screenshots of any UI changes for clarity.

Closing Issues: (if applicable)

• Mention any issues closed by this pull request using keywords like Closes #issue_number.

---

[mutheujoy]

@bdigismat check on this

[Dovineowuor]

Seems @bdigismat ain't up to it, please do update to help me update my fork effectively

[Dovineowuor]

@mutheujoy

[apexDev37]

Hey @Dovineowuor, thanks for the PR!

[apexDev37]

In the future, I propose trying to avoid long-lived branches that progress parallel to main. This way integration is easier, other contributors can pull in your patches/updates into their checkouts, and you can get faster feedback from a review

[apexDev37]

With that said, I'm happy to go through your changes🙂