fix harbor deployment

We don't yet support ports on harbor (see builds-api!50 (closed)), so this just does not use that.

With this patch, a fresh vargant run gets you a fully working environment where you can do:

dcaro@urcuchillay$ vagrant up
...
dcaro@urcuchillay$ vagrant ssh
...
vagrant@bullseye:~$ sudo -i -u toolsbeta.tf-test

toolsbeta.tf-test@bullseye:~$ toolforge build list
run_image    status    start_time    end_time    source_url    ref    repo_url    image_name    image_tag    builder_image

toolsbeta.tf-test@bullseye:~$ toolforge build start https://github.com/david-caro/wm-lol
Building 'https://github.com/david-caro/wm-lol', build name is 'tf-test-buildpacks-pipelinerun-4q7d4'
You can see the status with:
        toolforge build show

toolsbeta.tf-test@bullseye:~$ toolforge build logs
...

toolsbeta.tf-test@bullseye:~$ toolforge build show
Name: tf-test-buildpacks-pipelinerun-4q7d4
Start time: 2023-09-27T16:58:36Z
End time: 2023-09-27T17:00:56Z
Status: ok (Succeeded)
Message: Tasks Completed: 1 (Failed: 0, Cancelled 0), Skipped: 0
Parameters:
    source_url: https://github.com/david-caro/wm-lol
    ref: 
    image_name: tool-tf-test
    image_tag: latest
    repo_url: 172.19.0.1/tool-tf-test
    builder_image: toolsbeta-harbor.wmcloud.org/toolforge/heroku-builder-classic:22

Bug: T347401 Signed-off-by: David Caro dcaro@wikimedia.org