GitHub package contains a default site with one page peg a language tree only... I deployed packages, replicate both packages via a Package Manager, and activated /content/grs/en.html. en.html locks alike on the author and publish

It looks like you need to warp your filter as a custom bundle and deploy it to AEM.Some generic inputs about a bundle project could be found here https://docs.adobe.com/content/help/en/experience-manager-core-components/using/developing/archetype/core.html

Does it mean that you've installed AEM on TarMK and you want to use a MongoMK to store project's data?What is the use case of such a complex deployment? To make it happened you need to implement a MongoDB connector like to an external DB. I don't think we have any sample, but you can get an idea fro...

I managed to duplicate your issue myself. I found a configuration format that immediately turns IDP redirection: /apps/saml/config/com.adobe.granite.auth.saml.SamlAuthenticationHandler-mysaml.config Keep in mind, that after you deploy a package, you need to logout from AEM   

You might want to try ACS Tools VLT RCP. The tool has a GUI and it's easy to define source and destination: https://adobe-consulting-services.github.io/acs-aem-tools/features/vlt-rcp/index.html

AEM 6.3.3.0 you have to enable com.adobe.cq.dam.cfm.impl.conf.StructuredFragmentsFeature.config. Did you enable it?

The "src":"https:/admin:admin@<source-instance>/crx/server/crx.default/jcr:root/content/dam/we-retail/en/products/azcopy makes no sense.you cannot rcp by setting up the path from CRXDeYour source should be similar to https:/admin:admin@<source-instance>/content/dam/we-retail/en/products/azcopy

It's a limitation of AEM 6.3, You should plan an upgrade.As a workaround add configuration manually, for example: “cq:conf= /conf/we-retails” property into the Asset folder jcr:content node.

AEM Community is not available and not supported on AEM as a Cloud Service

We always recommend upgrading to the most recent SP. The Service Pack package also includes SP fixes and improvements. Available GitHub projects require a minimum version of 6.4.2 or 6.5. Both branches are equally supported.