Bump com.opentable.components:otj-pg-embedded from 0.13.4 to 1.0.2

[dependabot]

Bumps com.opentable.components:otj-pg-embedded from 0.13.4 to 1.0.2.

Changelog

Sourced from com.opentable.components:otj-pg-embedded's changelog.

1.0.2

• Internally split off from otj-parent to allow compatibility between different otj stacks and not pull as much otj-ness.

1.0.1

• Parent POM-328 changes see here

1.0.0

All the RC release features and fixes plus:

• Add network alias option
• Expose full bind mount function
• fix equals/hashcode in builder.

1.0.0RC3

• Stop excluding junit4 from testcontainers - check the README for the sordid details.
• Pass host and port to the ConnectionInfo bean. We strongly recommend you prefer getDatasource or getUrl, these will be more portable in usage. We ran into a few use cases where this was handy, however.
• LegacySingleInstancePostgresExtension to do the old Junit5 lifecycle behavior.
• 60 seconds default startup wait.
• Expose bind mounts (optional, none by default) in builder, currently hard coded as Read only.
• Expose network (optional, none by default) in builder.

1.0.0RC2

• Restore Java 8 compatibility
• Update to testcontainers 1.16.3

1.0.0RC1

• A completely rewritten version of otj-pg-embedded. Uses "testcontainers" for docker, while preserving API compatibility.

Advantages

• multi arch (m1 etc) support
• Works the same way on every OS - Mac, Windows, Linux. Please note the maintainers only test on Mac Linux
• You need a tarball for every linux distribution as PG 10+ no longer ship a "universal binary" for linux.
• Easy to switch docker image tag to upgrade versions.
• More maintainable and secure (you can pull docker images you trust, instead of trusting our tarballs)

Admittedly, a few disadvantages

• Slower than running a tarball
• A few compatibility drops and options have probably disappeared. Feel free to submit PRs
• Docker in Docker can be dodgy to get running.

... (truncated)

Commits

• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

Superseded by #310.