1.5.0

What's Changed

• CC-36943 Adjust vertex configuration validation by @vitaliiShveider in #7
• CC-36943 Update Readme with vertex backoffice configuration page by @vitaliiShveider in #6

Improvements

Added Back Office Configuration support to the Vertex module, with save-time validation that prevents the integration from being left in a broken state. Fully opt-in and backward compatible.

Configuration source

• Shared\Vertex\VertexConfig::isConfigurationModuleUsed() flag (default false) toggles the source. When on, Zed\Vertex\VertexConfig reads values from the spryker/configuration module (per scope: global/store) instead of config_default.php constants, and isActive() means "Vertex is the selected tax provider for the scope".
• New resolveConfigurationValue() / resolveModuleConfigurationValue() helpers and scope-aware getters.
• Schema resources/configuration/vertex.configuration.yml: Integrations → Vertex (credentials, Taxamo, invoicing, tax assist) and Taxes → Tax Provider.

Save-time validation — VertexTaxProviderPreSavePlugin:

• Blocks selecting Vertex as tax provider when its configuration is incomplete for that scope.
• Blocks credential changes/removals that would leave Vertex incomplete while it is the selected provider — including cross-scope (a global change that breaks stores inheriting the global config).
• URL fields (Security URI, Transaction calls URI, Taxamo API URL) must be valid URLs even when Vertex is not selected.
• Uses a sentinel pattern: pre-save plants markers on the values; the constraints (VertexTaxProviderConstraint, VertexConfigurationRemovalConstraint, VertexUrlConstraint) turn them into validation errors carrying the concrete reasons.

Full Changelog: 1.4.0...1.5.0