Merge #2668

2668: Start unbound with intended arguments r=mergify[bot] a=ScoreUnder

Unbound looked like it was meant to be started as if by `unbound -c /etc/unbound/unbound.conf`, but instead the string `-c /etc/unbound/unbound.conf` was set as argv[0] of the unbound command, meaning it is never parsed.

## What type of PR?

"Bugfix", but it works anyway without it -- it's just misleading to see a couple of arguments looking like they're being passed but actually just setting the display name of the process instead

## What does this PR do?

Calls execv with an argv list of 3 arguments (program name and intended 2 arguments) rather than just a program name. This appeared to be the intent of the original author.

### Related issue(s)

## Prerequisites
Before we can consider review and merge, please make sure the following list is done and checked.
If an entry in not applicable, you can check it or remove it from the list.

- [x] In case of feature or enhancement: documentation updated accordingly (n/a: bug)
- [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/workflow.html#changelog) entry file. (n/a: minor)


Co-authored-by: score <seejay.11@gmail.com>

optional/unbound/start.py

@@ -10,4 +10,4 @@ system.set_env()
 
 conf.jinja("/unbound.conf", os.environ, "/etc/unbound/unbound.conf")
 
-os.execv("/usr/sbin/unbound", ["-c /etc/unbound/unbound.conf"])
+os.execv("/usr/sbin/unbound", ["unbound", "-c", "/etc/unbound/unbound.conf"])