Use schema template for 403 errors

[lognaturel]

I noticed that https://docs.getodk.org/central-api-entity-management/#updating-an-entity has a 403 example with code and message both set to pencil. I imagine that's some fallback when no examples are specified.

We have a nice schema template for 403 errors so I went through and used that everywhere.

Some endpoints like the one above had 403s defined with json and json/extended response types. In those cases, I removed the json/extended one.

Some endpoints redundantly specified an example along with the schema reference which itself specifies the same examples. I removed the redundant ones.

Some endpoints have 403 responses with other response types (e.g. https://docs.getodk.org/central-api-form-management/#draft-form). I think that's also a mistake but didn't want to look too deeply into it for now.

What has been done to verify that this works as intended?

Rendered docs with make api-docs, spot checked a few 403s.

Why is this the best possible solution? Were any other approaches considered?

Yay for reduction of duplication.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Docs-only.

Does this change require updates to the API documentation? If so, please update docs/api.yaml as part of this PR.

This does update it.

Before submitting this PR, please make sure you have:

• run make test and confirmed all checks still pass OR confirm CircleCI build passes
• verified that any code from external sources are properly credited in comments or that everything is internally sourced

[matthew-white]

This is only sort of related, but one thing I'm wondering about is the code property of the Error403 schema. It looks to be a string, but Problem codes are actually numbers.

[lognaturel]

Great, we now have a single place to fix it! Let's roll it into this change.

I changed all the templates but didn't go through the ones that are defined inline.