Create multi-extension template

[tjcouch-sil]

As an extension developer, I want to create multiple extensions together and run them in Platform.Bible together in order to develop quickly and efficiently as well as to organize my code.

As a core developer, I want to create multiple extensions together and run them in Platform.Bible together in order to have one repository for the Paratext.Bible extensions where all my changes show up together for efficiency and organization.

We may be able to use merging subtrees to create a multi-extension template. We could have one repo that is a multi-extension template that has webpack config and such to support running multiple copies of the single extension template inside its src folder or something. There would be a bunch of extra config files in each extension folder that aren't typically used, but it would probably help merging to work more smoothly. And you could probably run each extension individually this way, too, which would be a benefit in some cases like if we made some sample extension repo that had a ton of little extensions in it.

[Sebastian-ubs]

https://discord.com/channels/1064938364597436416/1145779806684852285

[lyonsil]

This sounds more like submodules than subtrees, but I guess we'll see how it looks when someone investigates.

[tjcouch-sil]

PRs:
Added multi-extension template based on paranext-core/extensions by tjcouch-sil · Pull Request #1 · paranext/paranext-multi-extension-template
Prep for use in multi-extension-template by tjcouch-sil · Pull Request #55 · paranext/paranext-extension-template
Fixed a couple things related to packaging extensions by tjcouch-sil · Pull Request #2 · paranext/paranext-multi-extension-template
Added 'shared with' statements to various style files and brought them in sync by tjcouch-sil · Pull Request #3 · paranext/paranext-multi-extension-template
Added 'shared with' statements to various style files and brought them in sync by tjcouch-sil · Pull Request #56 · paranext/paranext-extension-template
Removed no-non-null-assertion as it is covered by no-type-assertion by tjcouch-sil · Pull Request #57 · paranext/paranext-extension-template
Removed no-non-null-assertion as it is covered by no-type-assertion by tjcouch-sil · Pull Request #4 · paranext/paranext-multi-extension-template

Wiki changes:
https://github.com/paranext/paranext-extension-template/wiki/Extension-Anatomy/_compare/034bea77f62284ea6b9102e2735240e71f0c24a1...1c6371176ebbab265fb286612dde745e685a59dd

[tjcouch-sil]

PRs implementing the template:
Rework extensions folder to use paranext-multi-extension-template by tjcouch-sil · Pull Request #693 · paranext/paranext-core
Add Word List and Text Collection by tjcouch-sil · Pull Request #1 · paranext/paratext-bible-extensions
Added 'shared with' on some files, updated copyright info, etc by tjcouch-sil · Pull Request #2 · paranext/paratext-bible-extensions

[roopa0222]

Testing Steps:
Cloned the repo from https://github.com/paranext/paranext-multi-extension-template

1. Created 2 extensions using the steps in the ReadMe.
2. Added 1 stand alone extension created from Paranext-extension-template.
3. Confirmed that all 3 Extensions displayed web-views without any errors.
4. Confirmed that all extensions are started at same time , so the data provider created in 1 extension is used in another without any errors.
5. Confirmed that 'npm run package' is building all individual extensions in release folder.