fix: wraft issues

[shahidvs]

Pull Request Description

Changes Made

• Feature addition
• Bug fix
• Performance improvement
• Refactoring
• Documentation update
• Other (please specify)

Description

functional fixes across the web and editor components

1. UI: Pagination Text Correction

• Fixed pagination display to correctly show the entry range

2. Web: Toast Notification Update

• Improved import success message to display the correct template name.

3. Editor: Sticky Toolbar Fix

• Made the editor toolbar sticky

4. Search Functionality in Variant Form

• added query for better search support

5. Null Value Handling in Block.tsx component

• Prevented potential crashes by safely handling null and undefined values.

6. Date Input Dark Mode Enhancement

• Improved calendar icon visibility in dark mode

7. Template Editor Variant & Dropdown Improvements

• Variant field now visible in both create and edit modes.
• Saved variant name is read-only in edit mode.
• removed "Edit" option from dropdown

8. Responsive Signup Form

9. Restrict Personal Workspace Features

• Blocked access to fields, members, roles, and permissions for personal organizations.
• Redirects restricted users to a 404 page.

10. Modal Outside Click Handler

11. Notification Sidebar Mode Integration

• create useNotificationSidebarMode hook.
• Integrated into personal workspace pages.
• To fix and improve sidebar behavior for Personal organization users when opening pages through notifications.

Related Issue

Fixes #(issue number)

Motivation and Context

• Improves UI clarity
• Enhances dark mode visibility and responsive design.
• Prevents crashes from invalid data
• Enforces correct access restrictions for personal workspaces

How Has This Been Tested?

• All changes verified in local and staging environments.
• Tested UI responsiveness, pagination, search, and modals.
• Verified editor, import, and sidebar behaviors
• Ensured dark mode and light mode compatibility.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My changes generate no new warnings.
• I have checked my code and corrected any misspellings.