fixes image path for dspace-postgres-pgcrypto

[balmas]

References

I didn't create an issue for this. Encountered as I was trying to complete the docker installation instructions for the configurable entities test data. (In case this is OS-specific, I'm running the install on Mac Sonoma 14.5 (Apple M3 Pro chip)

Description

Fixes the syntax in the path for the image for the postgres-pgcrypto image (I think all that was needed was to change :: to : but I also referenced the DOCKER-OWNER environment variable in the path for consistency with the other files.)

Instructions for Reviewers

List of changes in this PR:

• Changed the path to the image postgres-pgcrypto image

Confirm that command docker compose -p d8 -f docker/docker-compose.yml -f docker/docker-compose-rest.yml -f docker/db.entities.yml up -d succeeds.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• [ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• [ ] My PR passes ESLint validation using yarn lint
• [ ] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
• [ ] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• [ ] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• [ ] My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• [ ] My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• [ ] My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• [ ] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• [ ] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• [ ] If my PR fixes an issue ticket, I've linked them together.