Add setting to raise an error if asking for deprecated model about gto HOT 3 CLOSED

@aguschin - re: #68 (comment) - if an artifact has "labels", and possibly "status", it's worth figuring out whether "deprecated" is just another default status value, or maybe another distinct boolean property. 🤔 My current hunch says it's worth keeping as a unique boolean property. Especially if we might want logic relying on its existence/value, we need to allow it to coexist with any state/status

from gto.

Good question, @omesser!
Deprecated is a kind of different - at least now - because it can't be undone (I mean, you can delete git tag, but you cannot create new one that signals that deprecation is undone).
We can may make it another status value - a required one, but of that "status" which have only 1 value active for the specific artifact version. (as opposed to "env", when 1 specific version can be in many envs at once).

from gto.

No longer valid after #100.

from gto.