Upgrade `package_metadata` to 0.0.5 (was 0.0.2) (#2155)

**What type of PR is this?**

Other 

**What package or component does this PR mostly affect?**

go_repository
downstream extensions

**What does this PR do? Why is it needed?**

Downstream projects that depend on `gazelle` are adding the
`package_metadata` to their builds, e.g.
https://github.com/EngFlow/gazelle_cc/pull/72
The `package_metadata` 0.0.3 has added `licenses` rules that are missing
in 0.0.2.

When adding `gazelle_cc` via WORKSPACE we typically want to include
`gazelle` dependencies first before setting up extension specific
dependenices, example:
```
load("@bazel_gazelle//:deps.bzl", "gazelle_dependencies")
gazelle_dependencies()

load("@gazelle_cc//:deps.bzl", "gazelle_cc_dependencies")
gazelle_cc_dependencies()
```

Becouse older version of `package_metadata` would be requested in
`gazelle_dependencies` the newer version present in
`gazelle_cc_dependencies` would be ignored, making it hard to debug for
non experienced users.

By upgrading `package_metadata` to latest version we make dependency
resolution easier.


**Which issues(s) does this PR fix?**

No dedicated issue

**Other notes for review**

`package_metadata` should include the `license` attribute, but it can be
done in the follow up PR