Create and use nuget packages in libpalaso and related projects

[ermshiperete]

("packaging" below means creating the Debian packages)

• Create and use nuget packages in the following projects

  • libpalaso
  • chorus
  • flexbridge
  • liblcm
  • LfMerge
  • lfmerge-autosrtests
  • FieldWorks (the current work is in https://gerrit.lsdev.sil.org/c/FieldWorks/+/7869) (Use nuget packages in FieldWorks #1001)

• Verify that using the designer for winforms projects is still possible on Windows

  • test using the designer with VS 2019 16.8 in the projects
  • remove separate Designer projects that were added as a hack
  • test building on Linux
  • libpalaso
  • chorus (Allow to use WinForms designer chorus#224 currently fails on AppVeyor, maybe because it doesn't yet have the current VS version available) (Chorus: Verify that using the designer for winforms projects is still possible on Windows #1002)
  • flexbridge (FlexBridge: Verify that using the designer for winforms projects is still possible on Windows #1003)
  • liblcm (liblcm: Verify that using the designer for winforms projects is still possible on Windows #1004)
  • FieldWorks (FieldWorks: Verify that using the designer for winforms projects is still possible on Windows #1005)

• update flexbridge installer/packaging - adjust build scripts ([feature/nuget] Adjust changelogs flexbridge#289) (update flexbridge installer/packaging - adjust build scripts #1006)

  • Windows installer
  • Linux packaging

• update/test LfMerge packaging (update/test LfMerge packaging #1007)

• update/test FieldWorks packaging (update/test FieldWorks packaging #1008)

• document developing/debugging a project with dependencies that are now nuget packages (document developing/debugging a project with dependencies that are now nuget packages #1009)

• update and make available documentation of what changed and how things work now with the nuget packages (update and make available documentation of what changed and how things work now with the nuget packages #1010)

• update documentation with release process

• make the feature/nuget branch the main development branch

  • merge master into feature/nuget again on the different projects
  • announce that the merge of the feature/nuget branch will be made the main development branch
  • merge feature/nuget into master on the different projects. Doing this requires adjusting the path to the CHANGELOG.md file in the .csproj as well as adjusting GitVersion.yml (removing settings for feature/nuget branch).
  • create a release of the nuget packages on each project, and use these released nuget packages in the other projects. Note: also create releases for other projects like L10NSharp that still have a pre-release version number (Create release nuget packages of dependent projects #1018).
    • libpalaso (libpalaso: make the feature/nuget branch the main development branch #1011)
    • chorus (chorus: make the feature/nuget branch the main development branch #1012)
    • flexbridge (flexbridge: make the feature/nuget branch the main development branch #1013)
    • liblcm (liblcm: make the feature/nuget branch the main development branch #1014)
    • LfMerge (LfMerge: make the feature/nuget branch the main development branch #1015)
    • lfmerge-autosrtests (lfmerge-autosrtests: make the feature/nuget branch the main development branch #1016)
    • SIL.FwBuildTasks (SIL.FwBuildTasks: make the feature/nuget branch the main development branch #1017)
    • FieldWorks