Clean up restricted zones warning in code base to enforce separation of concerns

[twschiller]

Context

• We have an eslint rule to prevent separation of concerns:

  pixiebrix-extension/.eslintrc.js

  Line 8 in aa92de4

  ].map((exporter) => ({

• We introduced it to avoid issues importing code in contexts (contentScript, options page, etc.) that is not allowed by the Web Extension API model
• We can also use it to enforce separation of concerns between code modules

Steps to Reproduce

npm run lint -- --rule '{"import/no-restricted-paths": 2}'

Main sources of violations

• @/pageEditor/slices/editorSlice and related code
• @/contentScript/elementReference and related code
• @/pageScript/framework and related code
• @/pageEditor/testHelpers when used to test components in the context of a Page Editor form state
  • Proposed solution: allow use of @/pageEditor/testHelpers in .test.tsx files
• Analysis folder references Page Editor state. Ideally analysis folder is independent. (In future will want to run on server outside of extension context)

[BLoe]

Related: #4887

[github-actions]

This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.

[github-actions]

This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.

[github-actions]

This issue was closed because it has been stale for 7 days with no activity.