(zotero) Package is 32-bit only, but 64-bit application/installer is available

[teknowledgist]

Checklist

• I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
• I have verified that this is happening in the latest available version of the package.

Chocolatey Version

2.3.0

Chocolatey License

None

Package Version

7.0 - 7.0.3

Current Behaviour

The 32-bit version of Zotero installs on 64-bit systems, but since v7.0, there has been a 64-bit version available. Also, the 32-bit install of the application recognizes that it is on a 64-bit system and pops up a notice informing the user that the 64-bit version would be more efficient.

Expected Behaviour

The 64-bit version would install on 64-bit systems (absent forcing the 32-bit install).

Steps To Reproduce

1. On a 64-bit operating system, run choco install zotero or if a pre-v7 Zotero is already installed, run choco upgrade zotero.
2. Observe that Zotero is installed in the Program Files (x86) directory and/or run Zotero and a notice will appear about running 32-bit version on a 64-bit system.
   

Environment

* Windows 11 (23H1)
* Powershell (v5?)

Chocolatey Log

The log is unnecessary because it does not report an error.  The package is embedded and only contains the "win32" installer and the `chocolateyinstall.ps1` clearly only installs that.

Anything else?

No response

[hkdemiralp]

Zotero version 7.0.5 in chocolatey repo is still 32 bit. Switching to 64bit is seamless. Only a URL change in the choco package is enough to install 64 bit version. I had reported this at community discussions #2522 and package repo before. I hope it is updated soon.

[pauby]

@hkdemiralp This is a community repository. There is no one person responsible for the package in here. Pull requests are welcome.

[teknowledgist]

I have made a pull request.

Note: I don't have ready access to the official test environment, so someone else will need to test against that if it is absolutely required before merging. I see no reason to think that the changes might break what has already been working in the test environment, but I suppose those are famous last words.

[pauby]

@teknowledgist thanks for creating the PR. Running through the test-environment is always required before merging a PR.