nixgl: use original package name

[Smona]

Description

Some home manager modules depend on the name, so changing it in the wrapper can break them.

Fixes #6608

Checklist

• Change is backwards compatible.

• Code formatted with ./format.

• Code tested through nix-shell --pure tests -A run.all
  or nix build --reference-lock-file flake.lock ./tests#test-all using Flakes.

• Test cases updated/added. See example.

• Commit messages are formatted like

  {component}: {description}
  
  {long description}
  

  See CONTRIBUTING for more information and recent commit messages for examples.

• If this PR adds a new module

  • Added myself as module maintainer. See example.

Maintainer CC

[teto]

it's helpful to show in store path that it is a nixgl wrapper. I find it odd for a package to change its config based on its name. Maybe something to change more in the upstream package

[Smona]

That's a good point, I think this specific issue could possibly be fixed by using pname rather than name in the part of the chromium module highlighted here. I only went with this approach first because it would prevent instances of this problem in other modules from generating issues for the nixgl module going forward. I agree though that this change makes the store path less clear, so it's less than ideal.

[Smona]

I see @tadfisher authored that line, any thoughts on the alternative mentioned above?