Docker : Fix Dockerfile inspired by Kubo official Dockerfile

[FournyP]

Hi,

I've done this little change in the Dockerfile on my side for a personal project.

The build is clearly inspired by the official Kubo Dockerfile.
Imo it's make more sense than the older one.

It also bring the flexibility of the Kubo Dockerfile.

And the jq depency is downloaded in another FROM for paralleling purpose (as Kubo Dockerfile do in the utilities FROM).

Errors on the screen are because I didn't map the ports

Have a nice day

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions
  and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the
  rest) and in its best form. Follow the code contribution
  guidelines
  if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on
  any missing things and potentially assigning a reviewer for high
  priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

[lidel]

Triage notes:

• We will revisit this after Kubo 0.30 ships (Release 0.30 kubo#10436), making sure things run smoothly with the latest version

[lidel]

• TODO: switch to Kubo 0.30 once it ships

[lidel]

• Kubo 0.30 once it ships

[lidel]

@FournyP do you mind switching to Kubo 0.30 and confirming things work as expected?