fix: manually copy the contents of the .well-known directory to the d…

[erral]

…estination docker image

• I signed and returned the Plone Contributor Agreement, and received and accepted an invitation to join a team in the Plone GitHub organization.
• I verified there aren't any other open pull requests for the same change.
• I followed the guidelines in Contributing to Plone.
• I successfully ran code quality checks on my changes locally.
• I successfully ran tests on my changes locally.
• If needed, I added new tests for my changes.
• If needed, I added documentation for my changes.
• I included a change log entry in my commits.

---

If your pull request closes an open issue, include the exact text below, immediately followed by the issue number. When your pull request gets merged, then that issue will close automatically.

Closes #227 Ref #222

As messing with razzle.extend.js seems complicated, and as when running in development the .well-known URLs work perfectly, I thought that we can copy the contents of the .well-known folder directly to the docker image.

I tested it locally and it works.

[davisagli]

This makes more sense than spending a lot of time debugging the razzle build.

[Fosten]

This is exactly what I was going to suggest. LGTM.

[erral]

Thanks, let's how it behaves in testing.plone.org