Django check in CI is flakey because of plausible check

[obulat]

Description

Check this CI run: https://github.com/WordPress/openverse/actions/runs/4428714611/jobs/7768294796

Run Django check fails even though there are no changes to Django. (Actually, Django check shouldn't even run there?)

ERROR: for plausible  Cannot start service plausible: driver failed programming external connectivity on endpoint openverse_plausible_1 (1449e7e74b18855f73947ed4cd73f9e1c49ea8d90d610a119ef7683b389ab552): Error starting userland proxy: listen tcp4 0.0.0.0:50288: bind: address already in use

Priority set to medium because it usually passes when you re-run.

[dhruvkb]

This is a port binding issue we frequently see for API-level services running in the 502xx range. It has an existing issue #200 so it can possibly be closed.

This particular occurrence with Plausible will be reduced by #914 as only API-specific services will be created in the future.

Also the Django check will no longer run when #895 is merged.

[obulat]

Thank you for the explanation, @dhruvkb, I'll close this issue then.