BTCPay Server

This commit mainly adds the LUNO exchange as the default source for South African Rand (ZAR) exchange rates in BTCPay Server. It also includes a small hardening fix in another rate provider so that missing bid/ask values don't crash the app, plus a batch of unrelated test reliability improvements. There is no clear security vulnerability being patched.

This commit removes the old Selenium browser-automation test suite and its supporting infrastructure from the BTCPay Server project. It deletes test files, package references, Docker services, and CI job definitions, and updates two comments in production view files that previously mentioned Selenium. There is no change to the actual application code that users interact with, and no security fix or vulnerability is introduced.

This commit is purely a test-code reorganization. It moves several Playwright UI tests from one test file to another and creates a new dedicated WalletTests.cs file. No production application code was changed, so it cannot introduce a security vulnerability in the software users run.

This commit is a test-code refactoring: it moves existing webhook-related tests from several scattered test files into a single new file called WebhooksTests.cs. No production code is changed, and the commit message explicitly says it is just moving tests. There is no security fix or vulnerability here.

This commit only changes test code in BTCPay Server's PlaywrightTests.cs. It refactors how browser tabs are switched during automated UI tests and replaces some polling-style assertions with more direct Playwright expectations. There is no change to production code, no security fix, and no user-facing behavior change.

This commit fixes a flaky automated test for the crowdfunding feature. The test previously cleared a date field by directly manipulating the webpage's internal value, which was unreliable. The change makes the test click a visible 'Clear' button instead, and adds an ID to that button so the test can find it. There is no security issue here.

This commit fixes a potential server crash in BTCPay Server's error-handling page. Previously, if a visitor requested a non-HTML error page without specifying a status code, the code could try to use a missing value and throw a NullReferenceException. The change supplies a fallback 500 status code and renames a loop variable to avoid shadowing. It is a small defensive fix rather than a clear-cut exploitable vulnerability.

This commit is a straightforward code reorganization: it moves the Point of Sale (PoS) user-interface files from a shared views folder into the dedicated Point of Sale plugin folder, and updates the corresponding file paths in the controller and plugin registration. There is no functional change to how the application behaves, and no security fix or vulnerability is introduced.

This commit changes a single character in a test file, flipping a comparison operator from '==' to '!='. It is a test-only fix that corrects the logic of an assertion checking whether a UI alert appears. There is no change to production code and no security relevance.

This commit refactors how BTCPay Server stores labels for payment requests, moving them from a wallet-based graph system into new store-scoped database tables. It also adds a new API endpoint for updating store-scoped labels. The changes are primarily a feature/refactoring effort, but they include security-relevant hardening such as CSRF token validation on the new update endpoint, a check that the target store exists and matches the route, and restrictions preventing deletion or renaming of reserved system label types. A migration copies existing payment-request labels into the new tables and removes the old wallet-graph entries.

This commit is a purely cosmetic fix for a QR-code scan button icon in the wallet send page. It adjusts CSS margins and adds flexbox centering so the icon lines up correctly. There is no security relevance.