Migrate relevant 3.2 commits to the new branch structure

[handrews]

This includes the few commits that were:

• part of v3.2.0-dev
• not part of v3.1.1-dev
• not about removing the special Path Item Object $ref, or undo-ing that removal (let's just skip the whole thing...)

These were handled with git format-patch and git am, like we have been doing to sync different release lines. In some cases, I noticed that the anchors for the new fields were incorrect and fixed them as if they were git am merge conflicts (so there are not separate commits).

So this should be as close to what's on v3.2.0-dev in the versions/3.2.0.md file as we need it to be. But not identical.

[ralfhandl]

+1, one nit that I could address in a separate PR if I absolutely have to 😎

[mikekistler]

Looks good. 👍

[handrews]

@ralfhandl I merged your nit even though this was a port :-) Could you and @mikekistler please re-approve?

[ralfhandl]

@handrews Gladly, thanks!

[lornajane]

Changed to draft status to allow more discussion of the best way to add these and possibly other changes. There's more discussion on OAI/sig-security#12

[karenetheridge]

Looks like there would be schema changes to accompany these?

[handrews]

In the TDC Call we decided to defer CIBA to 3.3 based on OAI/sig-security#12 (if that somehow comes together quickly enough, it can get on the 3.2 train, but we won't hold up 3.2 since we're going to do 3.3 immediately after per #4210). I'm going to remove the CIBA commit(s) and take this out of draft.

@karenetheridge since this is just porting pre-existing work, please feel free to make a follow-up PR for the relevant schema changes on the v3.2-dev branch. I don't want to introduce new work in this PR.