Fix stale credential registry pins after vendor

On origin/develop 4a3bce011b these four tests fail. None of them touch Slack. Each one was confirmed on a bare develop checkout with `./dc test`: - `tests/test_credentials_connection_test.py::test_only_the_source_control_types_oauth2_and_headscale_set_the_https_only_flag`: the pinned set does not list `mcp_server`, which was added by Task 13366. - `tests/test_credentials_testers.py::test_no_post_ever_targets_an_operator_supplied_host[lightspeed]` and `[zoho_books]` fail with "made no request, so this asserts nothing". These are the W5 vendors from Task 13374. Their Test sends no request with the fixture config. - `tests/test_oauth2_connect_types.py::test_a_type_with_no_connect_provider_is_served_a_null_block`: `zoho_books`, `wave` and `lightspeed` became connectable without `_CONNECTABLE` being widened. They may also belong in the catalog-owned exclusion, `tests/credentials_helpers.py::CATALOG_TYPES`. Make each pin correct. Either update it, or move the catalog-owned types out of the hand-written pins as mem-36478 describes. If a vendor's Test should issue a request, fix that vendor spec instead of the test. Out of scope: Slack and Gmail connect, and any new vendor. Done means: the four tests pass on develop, and `./dc check quick` is green.

The four pins were already fixed on develop (171 passed). Fixed the api image build: check_docs_build.py was never copied in. Also removed the leftover duplicate pin lines. Quick gate green. PR #7914 merged as 9c7f1d2fea. Its deploy was superseded by later merges.