Move workspace addon to its own project

[grimsteel]

The docs imply that publishing a workspace addon from the same project as an editor addon temporarily disables the editor addon:

• https://developers.google.com/workspace/add-ons/how-tos/upgrade-addons
• https://developers.google.com/workspace/marketplace/list-multiple-app-integrations#add_app_integrations_to_an_existing_app_listing

This moves the Workspace addon, which has code for Docs and Sheets to its own folder/apps script project

[Divide-By-0]

Sweet! Did you test that the compilation looks good? Do I need a new .clasp.json for the workspace app?

[grimsteel]

Yes, you'll need to make a new project/clasp.json for the workspace app. (I was able to do clasp create then npm run clasp-push worked fine)

I did some basic testing in docs (both the editor and workspace addons) and sheets and rendering/derendering seems to be working as usual.