Update configuration-management.json

[bakasmarius]

Not sure if I added t3 correctly, it's this one: https://github.com/t3-oss/t3-env

-- EDIT:
Nevermind, I got it working 😅

[Maximization]

@bakasmarius Thanks for the PR! @t3-oss/env-core and envalid look good.

1. dmno is in maintenance mode and seems to recommend varlock instead:

Maintenance mode: DMNO receives critical bug and security fixes only. For a suitable replacement, see Varlock.

Should we add https://github.com/dmno-dev/varlock instead? Any experience with it?

2. znv is less popular and hasn't had a commit in 6 months. Since we already have plenty of options in this category, I'd say we leave this one out

[bakasmarius]

No, I haven't got any experience with varlock.
I was roughly comparing several options and finally went with zod 😆
I thought I'll add the ones I stumbled upon in the process.
So should I remove znv and dmno and add varlock?

[Maximization]

@bakasmarius Yes please! 🙏

[bakasmarius]

I'm having problems with varlock - the tests are failing, @Maximization could you please look into it?

[Maximization]

@bakasmarius all-the-package-names was outdated and didn't have varlock in the list. All good after updating. Sorry for the trouble! Now live at: https://nodejstoolbox.com/categories/configuration-management

[bakasmarius]

Ahh, great 😄
BTW, @t3-oss/env-cores description looks weird:
![NPM Version](https://img.shields.io/npm/v/%40t3-oss%2Fenv-core) [![JSR](https://jsr.io/badges/@t3-oss/env-core)](https://jsr.io/@t3-oss/env-core) [![JSR Score](https://jsr.io/badges/@t3-oss/env-core/score)](https://jsr.io/@t3-oss/env-core) [![Socket Bad

[Maximization]

@bakasmarius Thanks for catching that! Did a manual overwrite to: "Never build your apps with invalid environment variables again. Validate and transform your environment with ease." (from their website). Live at: https://nodejstoolbox.com/categories/configuration-management