According to https://github.com/torproject/torbrowser-launcher/pull/716
the definition of `gnupg_import_ok_pattern` in
`torbrowser_launcher/common.py` is causing some warnings.

But it looks like it is not being used since
83fa1d38, so we can remove it.

Thanks to meator for reporting the issue.

Update Tor Browser gpg key, with new expiration date on the current
subkey.

Set an environment variable to make it easier for Tor Browser to see
that torbrowser-launcher is being used.

Update Git repo URL in BUILD.md

See merge request !2

Update URLs in AppStream metadata

See merge request !1

Fix TBB archive name format

Closes #4

See merge request !3

Adapt AppArmor profile for Tor browser 13.0

Fix path variables in AppArmor profile

It is unclear to me what this is about.

We already allow ptrace for its relevant subprocesses via ptrace
rules, and I'm unsure if the full capability is really needed. I see
lots of other profiles which have ptrace rules without the capability
so I guess not. And I wonder if allowing the capability allows ptrace
for arbitrary processes, which would be really bad.

So let's assume it's not needed and we'll see what happens.

Firefox adjusts the OOM scores of its processes so that if they are
reaped they are killed in a sane order, e.g. the parent process last.

Source: hal/linux/LinuxProcessPriority.cpp

This "Firefox OpenGL probe utility" was added in Tor Browser 13.

Fix broken link to Tor signature verification site

Create bug_report.md

Minor cleanup

Add Turkish translation

Update Copyright to 2022

Allow github to recognize the License