Refactor lifecycle module names

[twschiller]

What does this PR do?

• Refactors naming in the lifecycle file and related content script messenger API
• Changes:
  • Extension Point -> Starter Brick
  • Extension -> Mod Component
  • Editor -> Draft
  • Persisted -> Activated
  • "tab" -> "frame" to clarify lifecycle runs in the context of a single frame
  • Use "install"/"run" terminology to match terminology in the Starter Brick interface: StarterBrick.install, StarterBrick.runModComponents
  • Use "remove" terminology to match terminology in the Starter Brick interface: StarterBrick.removeModComponent

Future

• For the PR, I erred on the side of naming consistency. There's some terminology we'll likely want to clean up in the future in the Starter Brick and lifecycle APIs
  • Move away from "install" terminology, because it can be confused with mod activation. Potential candidates: "mount" (confused with React lifecycle?), "attach", "initialize"
  • Move away from "run" terminology, because for some mod components, e.g., buttons/triggers, "running" the component means attaching it to the page, but the pipeline is not run until a user action/event. Potential candidates: "load", "initialize"
  • Move away from "remove" terminology, because it can be confused with mod deactivation
  • Move away from "reload" terminology, because it can be confused with window.load event terminology
• Rename the "Reactivate" brick external-facing terminology

For more information on our expectations for the PR process, see the
code review principles doc

[codecov]

Codecov Report

Attention: Patch coverage is 64.74359% with 55 lines in your changes missing coverage. Please review.

Project coverage is 73.74%. Comparing base (c32e86f) to head (39dd110).
Report is 50 commits behind head on main.

Files	Patch %	Lines
src/contentScript/lifecycle.ts	61.68%	41 Missing ⚠️
src/background/removeModComponentForEveryTab.ts	66.66%	3 Missing ⚠️
src/contentScript/messenger/api.ts	80.00%	2 Missing ⚠️
...Script/pageEditor/draft/updateDraftModComponent.ts	0.00%	2 Missing ⚠️
src/contentScript/pageEditor/resetTab.ts	0.00%	2 Missing ⚠️
src/bricks/effects/reactivate.ts	50.00%	1 Missing ⚠️
...tensionConsole/pages/brickEditor/useSubmitBrick.ts	50.00%	1 Missing ⚠️
...ionConsole/pages/settings/FactoryResetSettings.tsx	0.00%	1 Missing ⚠️
src/pageEditor/PanelContent.tsx	0.00%	1 Missing ⚠️
...pageEditor/hooks/useUpsertModComponentFormState.ts	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8708      +/-   ##
==========================================
+ Coverage   73.69%   73.74%   +0.05%     
==========================================
  Files        1344     1348       +4     
  Lines       41566    41728     +162     
  Branches     7775     7807      +32     
==========================================
+ Hits        30633    30774     +141     
- Misses      10933    10954      +21     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Playwright test results

 80 passed
 2 skipped

Details

 Open report ↗︎
 82 tests across 29 suites
 12 minutes, 34 seconds
 39dd110

Skipped tests

chrome › tests/runtime/googleSheetsIntegration.spec.ts › can activate a google spreadsheet mod with config options
edge › tests/runtime/googleSheetsIntegration.spec.ts › can activate a google spreadsheet mod with config options

[grahamlangford]

Looks great. Much easier to reason about with some of these name changes.

For the install/uninstall debate, I'm partial to attach/detach. I've run the concept through ChatGPT for other ideas, but attach still seems to be the best I've seen that's not overloading terms we use elsewhere. The few places we use attach in the existing codebase seem fairly consistent with the behavior we mean when attaching a starter brick

[github-actions]

No loom links were found in the first post. Please add one there if you'd like to it to appear on Slack.

Do not edit this comment manually.