feat: add build-info footer with version, commit SHA, and network (#952)

[temisan0x]

Closes #952

What changed

• added build-time env injection for:
  • app version
  • commit SHA
  • Stellar network
• added BuildInfoFooter component
• mounted footer in [locale]/layout.tsx
• added i18n keys for footer labels
• documented new env vars in .env.example

Notes

• commit SHA falls back to local if git metadata is unavailable
• backend /version support left for [Backend] Add GET /version endpoint exposing build SHA, build time, and contract IDs #881

Testing

• npm run build
• verified footer renders correctly

[temisan0x]

hey @ogazboiz, the backend and frontend failures are pre-existing on main — loanEndpoints, webhookRetryProcessor, and amount.test.ts are all untouched by this PR. Please let me know if you want me to rebase once those are sorted upstream

[ogazboiz]

hey, please rebase to pick up recent main changes — your CI is failing on issues that main has since resolved.

git fetch upstream
git rebase upstream/main
git push --force-with-lease

[ogazboiz]

conflicting with main now, please rebase (git fetch origin && git rebase origin/main && git push --force-with-lease) and i'll review the build-info footer plus the next.config/env changes.

if you want to keep contributing, join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0

[ogazboiz]

the build-info footer is a nice touch (version / network / commit sha, with the git rev-parse guarded by try/catch so it's safe when .git is absent). but it's on a very old base (its ci run predates the current green main by a lot) and it's conflicting, likely on next.config.ts / layout.tsx / en.json which moved on main. please rebase and re-verify the frontend build: git fetch origin && git rebase origin/main && git push --force-with-lease. if it stays red after the rebase i'll take another look.

if you want to keep contributing, join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0

[temisan0x]

Hi @ogazboiz, I’ve resolved the conflict and would appreciate your review.