Activity list page allows staff and educators to see unpublished activities

[brrkrmn]

Summary

With this PR, in the activity list page:

• Creators can only see the published activities
• Staff members and educators see a tab for published and unpublished activities
• Educators see all published activities and see their own unpublished activities
• Staff members see all published and all unpublished activities

Closes #1100

Changes

• Activities returned from getUnPublishedActivities are stored in unPublishedActivities instead of 'all_activities'
• Activities returned from 'getMyActivities' are stored in 'userActivities' instead of 'all_activities'

Screenshots

Creator view

Educator view

Staff view

[github-actions]

pre-commit checks failed ❌❌❌
make sure you have pre-commit set up locally (see the README.md for instructions).
If you have set up pre-commit locally, you may need to undo this commit and
run "pre-commit" locally to see what the errors are.

[github-actions]

pre-commit checks failed ❌❌❌
make sure you have pre-commit set up locally (see the README.md for instructions).
If you have set up pre-commit locally, you may need to undo this commit and
run "pre-commit" locally to see what the errors are.

[NdibeRaymond]

@brrkrmn can you check if we have t as part of the props passed to Activities? If we don't then something Is wrong and we should fix that (but not on this PR probably). However if t is in props then we should use it and not bother importing it again

[brrkrmn]

we have it in the props, changing the file now

[NdibeRaymond]

I think there are other PRs where you made translation changes to. For can check for this in those too

[github-actions]

pre-commit checks failed ❌❌❌
make sure you have pre-commit set up locally (see the README.md for instructions).
If you have set up pre-commit locally, you may need to undo this commit and
run "pre-commit" locally to see what the errors are.

[NdibeRaymond]

@brrkrmn I think merging master into your commit is causing the pre-commit action to try running for changes that are not introduced by this PR (and failing). while this is undesirable and should be fixed by me, something we can do is squash the three commits in this PR (the two commits introduced by you and the merge commit) into just one commit and force push

[NdibeRaymond]

If you don't know how to squash commits I can do that but then you'd have to do some kind of force-pull or delete and recreate the branch from the PR

[NdibeRaymond]

@brrkrmn I think merging master into your commit is causing the pre-commit action to try running for changes that are not introduced by this PR (and failing). while this is undesirable and should be fixed by me, something we can do is squash the three commits in this PR (the two commits introduced by you and the merge commit) into just one commit and force push

just squashing will likely not work here. Let me look at it and recommend exactly how to do it

[github-actions]

pre-commit checks failed ❌❌❌
make sure you have pre-commit set up locally (see the README.md for instructions).
If you have set up pre-commit locally, you may need to undo this commit and
run "pre-commit" locally to see what the errors are.

[NdibeRaymond]

I rebased on master git rebase -i master and force pushed to get rid of the merge commit (now the only commits left are yours).
Next up is, you have to update your local branch with this one, undo the remaining two commits with git reset --soft HEAD~2, then git add . and git commit. You will see the pre-commit errors you need to fix when you do this

alternatively, you can look at the failing pre-commit errors here https://github.com/unstructuredstudio/zubhub/actions/runs/8048977770/job/21981429416?pr=1114 (open Run pre-commit/[email protected]).
I identify the files with the failing pre-commit errors, introduce a useless change to those files (like a newline somewhere) and try committing. you should see the full list of pre-commit errors. Fix them and commit and the errors here should go away too

[github-actions]

pre-commit checks failed ❌❌❌
make sure you have pre-commit set up locally (see the README.md for instructions).
If you have set up pre-commit locally, you may need to undo this commit and
run "pre-commit" locally to see what the errors are.

[github-actions]

All pre-commit checks passed ✅✅✅

[NdibeRaymond]

@tuxology this has been rebased so we can focus on testing before merging to staging

[github-actions]

All pre-commit checks passed ✅✅✅