Add INTRODUCED property to all board configs

[igorpecovnik]

Pulling data that was stored in the current website's DB to the config. Adjusted accurancy with AI.## Summary

• Adds INTRODUCED year-range property to all 365 board config files
• Values: 2010-2015 (21), 2015-2020 (107), 2020-2025 (210), 2025-2030 (27)- Based on public release dates from manufacturer announcements

Test plan

• Verify build system ignores the new property (no functional impact)
• Spot-check a few boards against known release dates

[vidplace7]

👍 the boards I maintain are all correct

[github-actions]

✅ This PR has been reviewed and approved — all set for merge!

[HeyMeco]

Do we really need this tag though going forward?
Considering the SoC etc. is more important than when it was introduced.

[EvilOlaf]

I don't understand why this 5 year time window. I mean what prevents to simply do something like
for i in $(ls config/boards); do git whatevermagictoshowwhenthefilewascreatedbycommit |grep thisdate;done
To get the accurate year of introduction into the framework? Of course it is not the year of the introduction by the vendor but still close enough IMHO

[igorpecovnik]

Do we really need this tag though going forward?
I don't understand why this 5 year time window.

This information is only used to "filter out old boards", to find the board quicker. Nobody can recall when this board was introduced, but many recall approximate age. Time window makes more sense then accurate number. Of course we could store accurate year and have such filter on the download page itself.

I agree that "why time window" will rise questions and I already thought to rather have year here.

Since we now have also live search, we might rather drop this information altogether?

[EvilOlaf]

I don't believe that anyone will search by year to find a specific board. However I'd still keep the information for curious people who want to see which boards were introduced which year. Where latter the exact year would become handy. Overall its a nice-to-have information only.

[EvilOlaf]

introduced...EvilOlaf:build:introduced
Not perfect, needs some tweaking since some board configurations have more than one comment at the very beginning. Also some boards are using declare -g while most do not. However cleaning this mess up is a different task

[igorpecovnik]

Not perfect,

Commit log is not very accurate. I told AI to scrap this info first from our website following by comparing with what he can find on the web. Pusing my approach soon.

[Grippy98]

Looks fine to me but also clutters the board a bit and not sure how useful this is compared to what SoC they have like Maco mentioned.

[github-actions]

✅ This PR has been reviewed and approved — all set for merge!