Add value/codigo machine-key column to lookupOptions

accessRequestStatus (and likely other groups) has no differentiated campo — all rows in a grupo share the same literal campo string, only nombre (Spanish label) differs. This forces label-text matching in views/code (e.g. vOpenAccessRequests PLUTO-550 uses WHERE nombre NOT IN (...) as an interim). evolutiva-commons.md §Lookup-Backed-Columns already mandates an authored value/codigo column per option, not label-derived. Fleet-wide scope: touches lookupOptions schema + every callsite currently matching on nombre across groups that lack campo differentiation. Low priority, not blocking PLUTO-550.