APERTA-10963 preprint doi in paper tracker requires flag

[amaxsurge]

JIRA issue: https://jira.plos.org/jira/browse/APERTA-10963

What this PR does:

At /paper_tracker the preprint doi column is now hidden unless the corresponding preprint flag is checked

Special instructions for Review or PO:

Toggle the flag checkbox, view the column

Code Review Tasks:

Author tasks (delete tasks that don't apply to your PR, this list should be finished before code review):

• If I made any UI changes, I've let QA know.

Reviewer tasks (these should be checked or somehow noted before passing on to PO):

• I read through the JIRA ticket's AC before doing the rest of the review
• I ran the code (in the review environment or locally). I agree the running code fulfills the Acceptance Criteria as stated on the JIRA ticket
• I read the code; it looks good
• I have found the tests to be sufficient for both positive and negative test cases

[amaxsurge]

Notes to reviewer.

1. For reasons that I cannot fathom the code changes (not the test changes) are causing failures here in the paper tracker test with no meaningful error message except a reference to a 404 that does not show up in the network console

2. I went down a whole rabbit hole here trying to test the positive case where you need inject and update a service into the global container. As far as I can tell based on this
   https://stackoverflow.com/questions/28422375/how-to-mock-an-ember-cli-service-in-an-acceptance-test
   and
   Allow overriding services/factories in the registry. emberjs/ember-test-helpers#96

this is only possible in a moduleForComponent based test but not a plain acceptance test. Would be happy to be corrected on this if anybody knows how to do it.

[egh]

Per AC 2 this should be "Pre-print DOI"

[amaxsurge]

crazy, I swear I did that. Must have stashed it or something. thanks

[egh]

@amaxsurge I believe the test problem is due to the feature flag service not being stubbed out. See https://github.com/Tahi-project/tahi/blob/master/client/tests/integration/pods/components/admin-page/component-test.js#L19 for an example, but I can't get this to work directly with your test, probably because of some strange difference between qunit test types.

[amaxsurge]

@egh yeah I basically wrote that exact same code that you put in the example and could not get it to work. Let me keep reading and playing with it

[amaxsurge]

@egh all tests are passing here. Is this still in review?

[egh]

👍