Use development build flag in Build Desktop

[neuronull]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-28826

📔 Objective

While working on enabling easier access to the dev logs, I realized that we aren't building the desktop artifacts in Build Desktop workflow with the NODE_ENV=development flag. The result is that even if you set RUST_LOG=debug , the logs don't make it to the on-disk file because they are filtered out at the electron level.

This change builds the desktop artifacts with the dev flag.

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

Checkmarx One – Scan Summary & Details – 12192a99-5a55-479c-a956-d76f73f4063a

Great job! No new security vulnerabilities introduced in this pull request