The current local development environment for developer-portal uses curl to call blubberoid and generate a Dockerfile which is then used from the docker-compose.yaml to build the runtime container for developer-portal itself. Now that Blubber publishes a buildkit frontend, we can use it rather than blubberoid.

This will look something like:

• Add a # syntax=docker-registry.wikimedia.org/wikimedia/blubber-buildkit:<some tag> directive to the top of .pipeline/blubber.yaml
• Change docker-compose.yaml's portal.build.dockerfile value to .pipeline/blubber.yaml
• Add a portal.build.target value of local to docker-compose.yaml
• Remove legacy .pipeline/local.Dockerfile
• Remove legacy Makefile instructions for generating .pipeline/*.Dockerfile files