Add store-scoped discount management to Grand.Web.Store

[Copilot]

Store owners had no way to manage discounts from the store area — only admins could via Grand.Web.Admin. This adds a full discount CRUD surface to Grand.Web.Store with all operations scoped to the current store owner's store.

Controller (DiscountController.cs)

• List/Create/Edit/Delete with AccessToEntityByStore(CurrentStoreId) guards on all mutating actions
• Create and Edit force model.Stores = [CurrentStoreId] — store owners cannot assign discounts to other stores
• Coupon codes, discount requirements, applied-to (products/categories/brands/collections), and usage history fully supported
• No IsStoreManager check needed — all users in the Store area are implicitly store managers
• GetDiscountRequirementConfigurationUrl calls IDiscountRule.GetConfigurationUrl(..., area: "Store") directly, producing area-correct URLs without any string replacement

Views (Areas/Store/Views/Discount/)

• Full view set adapted from Grand.Web.Admin with Constants.AreaStore throughout
• Stores field omitted from TabInfo — assigned server-side automatically
• Vendor tab omitted — not applicable in store context
• Brand/collection/product add-popups scope their search queries to CurrentStoreId

Discount requirement plugin support (DiscountRules.Standard)

• IDiscountRule.GetConfigurationUrl gains an optional area = "Admin" parameter — providers use it to build area-aware URLs without hardcoding Admin/
• New BaseDiscountRulePluginController shared base class with [AuthorizeAdmin(ignore: true)], [Area("Admin")], [AuthorizeMenu] — bypasses the admin-only gate so store managers can reach the same controllers; per-action authorization via IPermissionService is preserved
• All 5 Admin plugin controllers (CustomerGroups, HadSpentAmount, ShoppingCartAmount, HasOneProduct, HasAllProducts) now carry dual [Route] attributes (Admin/[controller]/[action] and Store/[controller]/[action]), serving both areas without any view duplication
• HasOneProduct and HasAllProducts check CurrentStoreId and scope product search and available stores to the store manager's store when accessed from the Store area

Store scoping

The list query already filters by StaffStoreId inside DiscountViewModelService.PrepareDiscountModel — no service changes needed.

_ViewImports.cshtml

Added @using Grand.Web.AdminShared.Models.Discounts to the Store area view imports.

[Copilot]

@copilot Disocunt requirements does not work, because refers to the plugin DiscountRules.Standard and this plugin use Admin authorization

Fixed. The root cause was that DiscountRules.Standard plugin controllers inherit BaseAdminPluginController which carries [AuthorizeAdmin] — an attribute that explicitly redirects store managers to the admin login page.

The fix adds Store-area counterparts throughout:

1. BaseStorePluginController (Grand.Web.Common/Controllers/) — new base class with [AuthorizeStore], [Area("Store")], [AuthorizeMenu]
2. 5 Store-area controllers in DiscountRules.Standard/Areas/Store/Controllers/ — mirror of the Admin ones, using BaseStorePluginController; product search in HasOneProduct/HasAllProducts is scoped to the store manager's store
3. Store-area views in DiscountRules.Standard/Areas/Store/Views/ — vendor fields omitted; Url.Action(...) used instead of Url.RouteUrl(named-route) so resolution is area-context-aware
4. DiscountController.cs (Store area) — GetDiscountRequirementConfigurationUrl and GetDiscountRequirementMetaInfo now call a BuildStoreRequirementUrl helper that rewrites the Admin/ path prefix to Store/ before returning the URL to the browser

Commit: the changes span commits ending at the latest push.

[Copilot]

@copilot solution with changes in plugins is a copy of code, It's better to change logical for Url for discount provider

Addressed in the latest commit. The approach now avoids all code duplication:

1. IDiscountRule.GetConfigurationUrl gains an optional area = "Admin" parameter — providers construct the URL using the area directly instead of hardcoding Admin/.

2. BaseDiscountRulePluginController — a new shared base class with [AuthorizeAdmin(ignore: true)] + [Area("Admin")] + [AuthorizeMenu]. Bypassing [AuthorizeAdmin] (which blocks store managers) means the same Admin-area controllers serve both Admin and Store requests. Per-action authorization via IPermissionService.Authorize(StandardPermission.ManageDiscounts) is preserved.

3. Dual [Route] attributes on all 5 Admin plugin controllers — [Route("Admin/[controller]/[action]")] + [Route("Store/[controller]/[action]")]. ASP.NET Core resolves views from Areas/Admin/Views/ regardless of which route was matched (because [Area("Admin")] is set on the base class), so no view duplication is needed.

4. Store-manager context in HasOneProduct/HasAllProducts — ProductAddPopup and ProductAddPopupList check CurrentStoreId and scope available stores/product search accordingly.

5. Deleted all Store-area plugin controllers/views (13 files) and BaseStorePluginController — no more duplication.

[Copilot]

@copilot Grand.Web.Store Discount requirements - Discount rule: Must be assigned to customer group: Url referes to //Store/CustomerGroups/Configure/?discountId=6a1c874ec21f1d98a3dd2d94
in the admin i...

Fixed in the latest commit. The root cause was that class-level [Route] attributes on the plugin controllers prevented ASP.NET Core's conventional routing from dispatching to those controllers — meaning the EndpointProvider.cs conventional routes had no effect.

The fix:

1. Removed the [Route] class-level attributes from all 5 plugin controllers (CustomerGroups, HadSpentAmount, ShoppingCartAmount, HasAllProducts, HasOneProduct) — this restores conventional routing, consistent with all other GrandNode plugins.
2. Added Store/ conventional routes to EndpointProvider.cs for each plugin controller action, mirroring the existing Admin/ routes. The storeareas route (Store/{controller}/{action} with area=Store) doesn't cover these controllers since they are in the Admin area, so explicit routes are required.
3. Added the missing Admin/ShoppingCartAmount/Configure conventional route to EndpointProvider.cs (it was always handled by the general adminareas route, but adding it explicitly is consistent with the pattern for the other four controllers).

With this, /Store/CustomerGroups/Configure/?discountId=... now routes to CustomerGroupsController.Configure, which is accessible to store managers via [AuthorizeAdmin(ignore: true)] on BaseDiscountRulePluginController.