issue resolve - showing new projects dynamically

[vivekCS007]

Description
Replaced the static “Projects in 2024” grid with a dynamic {% for project %} loop so the UI renders whatever the backend passes in.
Extended populate_projects to pull live repo metadata from the ContriHUB org, parse push timestamps, filter by recent activity/name heuristics, and fall back to the legacy allowlist only when nothing qualifies.
Stored extra GitHub data (description, homepage, topics, pushed_at) on each project and surfaced them in the card layout.
Related Issue
Fixes #194

Type of change
New feature (non-breaking change which adds functionality)
Motivation and Context
The projects page was frozen with hard-coded 2024 entries. These changes keep the page current by syncing from GitHub and rendering the data dynamically without manual edits each season.

How Has This Been Tested?
python manage.py migrate (SQLite override)
python manage.py shell → Client().login() → /project/populate_projects/ and /project/; verified HTTP 200 and non-zero is_current count.
python manage.py runserver → manual smoke test at http://127.0.0.1:8000/project/ confirming dynamic cards render with description/topics/homepage/last-updated details.
Screenshots (if appropriate):

Checklist:
✅ I have registered myself at Contrihub website.
✅ My code follows the code style of this project.
I have commented my code, particularly in hard-to-understand areas
✅ My changes generate no new warnings
My change requires a change to the documentation.
I have updated the documentation accordingly.
✅ I have read the CONTRIBUTING document.
✅ Any dependent changes have been merged and published in downstream modules
I have added tests to cover my changes.
✅ All new and existing tests passed.
Test Configuration:

Firmware version: N/A
Hardware: HP Victus 16
Toolchain: Python 3.9.23 / pip 25.2
SDK: Django 4.1

[lokesh-wagh]

how are you differentiating from the repos present in last year's contrihub from the current one

[vivekCS007]

sir in the project/views.py file in line 36-67 we firstly pull repo["pushed_at"] and convert into date time format then captures current time, then it is defined in the tokens in 3-4 ways it checks within 365days of interval from the current time whether an repo's year is in currentyear-1 or not, then flag repo as current if it is.
now = timezone.now()
year_tokens = {
str(now.year),
str(now.year - 1),
str(now.year)[-2:],
str(now.year - 1)[-2:],
} this is one of code snippet

[lokesh-wagh]

create a new PR as the dashboard crashes whenever it is opened after merging your PR