harbor update to 1.18.3-bb.0

Package Merge Request

Package Changes

https://repo1.dso.mil/big-bang/product/packages/harbor/-/blob/1.18.3-bb.0/CHANGELOG.md

Package MR

big-bang/product/packages/harbor!213 (merged)

For Issue

Closes big-bang/product/packages/harbor#170 (closed)

Upgrade Notices

Known upstream bug (goharbor/harbor#22996): The IronBank v2.15.0 image was built before upstream fix PR #22998 was cherry-picked to the release branch. The ca_certificate column addition was incorrectly placed in migration 0171 (a v2.14.1 file) instead of a new 0180 file. When upgrading from v2.14.x, golang-migrate skips the modified 0171 since the schema is already at version 171, causing the Registries page to return internal server error (column t0.ca_certificate does not exist).

Workaround: After upgrade, run against the Harbor database:

ALTER TABLE registry ADD COLUMN IF NOT EXISTS ca_certificate TEXT;

Then restart harbor-core pods. This will self-resolve when IB rebuilds from the final v2.15.0 tag which includes migration 0180_2.15.0_schema.up.sql.