Add additional logging to custom import task

[bmclaughlin]

Adds conditional logging based on if GALAXY_ENABLE_API_ACCESS_LOG is enabled then logs collection details to the api access log in the galaxy_ng_worker_1 container where the uploads occur.

Log:

2021-12-02 18:13:54,441: INFO: Anonymous uploaded collection: newswangerd-collection_demo-1.0.11

Issue: AAH-1018

[bmclaughlin]

/retest

[awcrosby]

are there any unit or functional tests for api logging where this msg could be added?

[patchback]

Backport to stable-4.4: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply e74ea6b on top of patchback/backports/stable-4.4/e74ea6b1b7cb51594b3174d12554e5e4ea9717f7/pr-1069

Backporting merged PR #1069 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/galaxy_ng.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-4.4/e74ea6b1b7cb51594b3174d12554e5e4ea9717f7/pr-1069 upstream/stable-4.4

4. Now, cherry-pick PR Add additional logging to custom import task #1069 contents into that branch:

   $ git cherry-pick -x e74ea6b1b7cb51594b3174d12554e5e4ea9717f7

   If it'll yell at you with something like fatal: Commit e74ea6b1b7cb51594b3174d12554e5e4ea9717f7 is a merge but no -m option was given., add -m 1 as follows intead:

   $ git cherry-pick -m1 -x e74ea6b1b7cb51594b3174d12554e5e4ea9717f7

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Add additional logging to custom import task #1069 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4.4/e74ea6b1b7cb51594b3174d12554e5e4ea9717f7/pr-1069

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.