implemented half lap joint

[jonashaldemann]

Implemented a new joint type: Half-lap joint.

What type of change is this?

• Bug fix in a backwards-compatible manner.
• New feature in a backwards-compatible manner.
• Breaking change: bug fix or new feature that involve incompatible API changes.
• Other (e.g. doc update, configuration, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I added a line to the CHANGELOG.md file in the Unreleased section under the most fitting heading (e.g. Added, Changed, Removed).
• I ran all tests on my computer and it's all green (i.e. invoke test).
• I ran lint on my computer and there are no errors (i.e. invoke lint).
• I added new functions/classes and made them available on a second-level import, e.g. compas_timber.datastructures.Beam.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if appropriate)

[chenkasirer]

Looks great, Jonas!

1. i've implemented a more proper solution to this brep from mesh hack, once it's ready to use we can change it together.
2. run invoke format and it'll automatically re-format your code
3. run invoke lint, it'll then tell where exactly there are linting/formatting issues which you will have to fix manually.
4. See other comments below.

[chenkasirer]

@jonashaldemann fix is merged so if you merge main onto your feature branch you should be able to use the latest COMPAS core commit.

[chenkasirer]

LGTM. left a couple of comments, please have a look before merging.

[chenkasirer]

I'd suggest moving this line to below all the input validity checks below. Otherwise it might try to calculate the distance even when there's no valid input.

completed requested changes