bug_report.md: remove confusing 'maintainer information' section

[Atemu]

Motivation for this change

When I started out, I was confused by this section and no idea what to put in
and I don't think I'm the only one as I rarely see it filled out.

This means there isn't much usefulness in it for bot processing either; better
just remove it.

cc @zimbatm

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[cole-h]

Maybe the wording could be updated to just ask the submitter to ping any maintainers / people who have touched that package / module before (guide them to look at git blame / GitHub's UI for that)? I don't typically monitor Nixpkgs issues, so it's helpful for people who have issues with modules or packages of mine to ping me.

[stale]

I marked this as stale due to inactivity. → More info

[zimbatm]

Fair enough. I had some ideas with that section but it needs to be generated automatically to be useful and can be re-introduced later if needed.

@Atemu mind updating the PR?

[Atemu]

Oh! Didn't know there was a conflict, will update it right away.

Can I somehow get github to tell me when that happens again in the future?

[roberth]

It didn't confuse me and I think I wrote valid yaml...

Was looking forward to some stats based on the data, but I guess it didn't work out that way.

[zimbatm]

Making a call to remove it. This was a half-assed attempt at collecting package meta-data. Let's re-add it with some proper tooling that can generate the issue template.