Finish changing the development containers idea of where artifacts live

[rjsparks]

drafts, for instance, in production, live in /a/ietfdata/doc/draft/archive and /a/ietfdata/doc/draft/repository.

The dev container should mirror that structure using /assets/ietfdata/a/draft/archive at least (though we should allow live verification that the right things happen with handling the repository as well.

but right now:

INTERNET_ALL_DRAFTS_ARCHIVE_DIR = /assets/archive/id
INTERNET_DRAFT_ARCHIVE_DIR = /assets/archive/id
INTERNET_DRAFT_PATH = /assets/ietf-ftp/internet-drafts/

[rjsparks]

Also

IDSUBMIT_REPOSITORY_PATH = "test/id/"

We need to revisit why we even have an IDSUBMIT_REPOSITORY_PATH that's different from INTERNET_DRAFT_PATH at this point. Further, that one should probable buy renamed INTERNET_DRAFT_REPOSITORY and the archive settings above should combine to INTERNET_DRAFT_ARCHIVE, and have the trailing slash or not rationalized.

The history of pre-containerized development are what led us to having so many knobs for almost the same thing.

[rjsparks]

This is probably going to have us also pull ghostlinkd into the app container (until we start using something else in production).

[rjsparks]

This might also turn into a forcing function for finishing the move of artifacts out of www6s into /a/ietfdata