Answer
Check whether this matches a known, already-identified defect for your upgrade path before assuming your own field configuration changed — this specific symptom (fields rendering as mandatory despite not being configured that way) has occurred as a confirmed platform defect on more than one release line, with fixes released rather than a configuration cause.