Add env-guard to DevOps section

[miit-daga]

This pull request adds env-guard to the DevOps section of the awesome database tools list.

What was added:

• env-guard - Schema-based validator for environment variables with TypeScript support for database configuration validation.

Why it fits in DevOps:
Env-guard is a zero-dependency Node.js library that provides schema-based validation of environment variables, with built-in support for CI/CD integration. It helps prevent configuration errors in database setups by validating env vars at runtime, making it a valuable tool for DevOps workflows involving database configuration management.

Placement:
The entry has been added alphabetically in the DevOps section, positioned between DBmaestro and Toad DevOps Toolkit.

This addition enhances the list by including a modern, TypeScript-supported tool for environment variable validation in database-related DevOps pipelines.

[miit-daga]

@mgramin Hello!
It's been quite a while since I opened this PR. Can you please check it and merge it if it's fine?
Thank you!

[miit-daga]

@mgramin Hello!
Just a gentle reminder.
It's been quite a while since I opened this PR. Can you please check it and merge it if it's fine?
Thank you!

[mgramin]

@miit-daga Hello!

Thanks a lot for the PR and for your continued interest in awesome-db-tools — I really appreciate your previous contribution, it was a great addition 👍

I’ve taken a careful look at env-guard, and the project itself looks solid and well-implemented. That said, at this point I don’t feel comfortable merging it into the awesome list.

The main reasons are:

• the project is still very young and early-stage
• its connection to database tooling is not very clear yet, as the use case seems quite narrow and mostly focused on a specific TypeScript workflow

For this list, I try to keep tools that are either clearly DB-focused or have already proven broader adoption and usefulness in the database ecosystem.

This is absolutely not a statement about the quality or potential of your project — many tools simply need some time to mature and find their audience. Feel free to come back later when the project has evolved further or its DB-related use cases are more established. That’s a pretty common situation for awesome lists.

Thanks again for sharing your work and for understanding!