Use deco from JSR

## Issue Type

Please inform the type(s) of issue(s) you are reporting:

- Feature Request

## Description

This PR migrates the project to use `@deco/deco` via JSR instead of the previous HTTP imports. The change touches multiple files within the application as it updates the imports from `deco/` to `@deco/deco` across all modules.

### Key Changes:
- Updated import paths from `deco/` to `@deco/deco`.
- This update affects numerous files across the project’s apps, ensuring all modules adopt the new import path.
- This migration is part of an ongoing effort to streamline and optimize our workflow.

## Steps to Reproduce (for bugs)

1. N/A – This is a feature request and enhancement.

## Expected Behavior

- Project should use JSR for `@deco/deco` imports, resulting in faster downloads and better package management.
- Language server protocol (LSP) integration should improve, enhancing developer experience.
- Removing the necessity of including Deco’s import map in target projects.

## Actual Behavior

- Prior to this change, the project relied on HTTP imports, which required Deco’s import map in each target project and slower package downloads.

## Additional Context

### Next Steps:
- A migration script will be created to assist in transitioning existing sites to use `@deco/deco`.
- Eventually, a monorepo structure will be introduced to house all JSR apps within the `apps` directory.

### Motivation:
- **Faster Downloads**: JSR enables more efficient package resolution.
- **Simplified Project Setup**: No need to include Deco’s import map in each project.
- **Improved LSP Support**: JSR packages enhance LSP functionality for a better developer experience.

---

Thank you for taking the time to report this issue!