Updates the relationship for committees to officers to be a hasMany relationship, as we have multiple officers under the General committee, but the relationship didn't reflect that.
This resolves the issue where scoping committees by active officers (via an include) was resulting in duplicate committees (as each officer had "their own" General committee)
This looks good to me. Asking for additional eyes though since this would be a DB change and could cause issues in prod if there is a problem with migrations.
Updates the relationship for committees to officers to be a hasMany relationship, as we have multiple officers under the General committee, but the relationship didn't reflect that. This resolves the issue where scoping committees by active officers (via an include) was resulting in duplicate committees (as each officer had "their own" General committee)