chore: Overriding the import @appsmith eslint rule on EE folder

[ankitakinger]

Description

Overriding the import @AppSmith eslint rule on EE folder

PR fixes following issue(s)

Fixes #24183

Type of change

• Chore (housekeeping or task changes that don't impact user perception)

Testing

How Has This Been Tested?

• Manual
• Jest
• Cypress

Checklist:

Dev activity

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• PR is being merged under a feature flag

QA activity:

• Speedbreak features have been covered
• Test plan covers all impacted features and areas of interest
• Test plan has been peer reviewed by project stakeholders and other QA members
• Manually tested functionality on DP
• We had an implementation alignment call with stakeholders post QA Round 2
• Cypress test cases have been added and approved by SDET/manual QA
• Added Test Plan Approved label after Cypress tests were reviewed
• Added Test Plan Approved label after JUnit tests were reviewed

[what-the-diff]

PR Summary

• Removal of .eslintrc file in the ee directory
  The .eslintrc configuration file located in the ee directory was removed.

• New restricted imports rule added
  A rule for restricted imports was added to the .eslintrc file in the app/client/ directory, applying only to files under the /ee//* path. This rule filters out any rules specifically related to the ce code (those with a group of "**/ce/*").