Possibility to override min-age for specific packages

[aleksandrs-ledovskis]

Some Homebrew packages are being updated on the ever so frequent cadence. Especially the Casks like web browsers ("google-chrome", "chromedriver"), editors ("visual-studio-code", "zed") or when using "@beta", "@nightly" modifiers.

It would be valuable if end-user of "brew-safe-upgrade" could mark that a package "X" is checked against a different (even a 0) value for min-age check.

The implementation would likely require a some form of a persistent configuration for the "brew-safe-upgrade". Options may vary from a simple TOML/JSON at a ~/.config/ path to a something more robust like a SQLite DB.