feat(file imports): adds an experimental IFC parser

[adamhathcock]

• experimental IFC parser can be toggled via feature flag, featureFlags.fileImportIFCDotNetEnabled in Helm Chart or FF_FILEIMPORT_IFC_DOTNET_ENABLED environment variable on the fileimport service in Docker Compose or local development environment.
• Experimental IFC parser is built in .Net
• File Import service Docker image is now based on Ubuntu and not Debian (distroless).
• Example IFC files are now located in packages/fileimport-service/ifc-dotnet/ifcs

[adamhathcock]

@iainsproat I think I fixed everything about docker....need confirmation of the corepack change

[github-actions]

📸 Preview service has generated an image.

[github-actions]

📸 Preview service has generated an image.

[github-actions]

📸 Preview service has generated an image.

[adamhathcock]

Two of the example files are failing on the step parser. I think it's because of whitespace/separator intolerance.

[iainsproat]

@adamhathcock - do we have a better way of managing/importing wasm files, so that the provenance can be known and followed by a community member? #3525 (comment) edit: discussed and this was an existing file, so we will keep as is

If the two example files can be shown to pass the revised IFC parser, I'd be happy to approve for merging. We can then enable the feature flag on latest and have the wider team test it.

We still need to investigate the file provided via speckle.community which was causing high memory usage. I don't consider it a blocker to merging though. It was reported as working on the original node js IFC parser if its memory limit is increased to 4Gi. What upper bound of memory is required for the .Net parser? Is there a memory leak or other memory-usage inefficiency we can resolve?

[github-actions]

📸 Preview service has generated an image.

[iainsproat]

Appears to be about parity with the existing connector with respect to the example IFC models I have to hand.

[adamhathcock]

Need @gjedlicska to approve and merge