Fix errors encountered in feature testing.

[kshitij01042002]

Overview

1. This PR fixes or fixes part of #[fill_in_number_here].

2. This PR does the following: This PR fixes the API access for the new contributor dashboard.
   This error was recognixed during feature testing.

3. (For bug-fixing PRs only) The original bug occurred because: Used the API which had access to only super admins, so made the get API access open.

Because of introduction of new roles and new feature needed to update the access according to the feature flag.

Essential Checklist

• The PR title starts with "Fix #bugnum: " or "Fix part of #bugnum: ...",
  followed by a short, clear summary of the changes.
• I have followed the instructions for making a code change.
• The linter/Karma presubmit checks have passed on my local machine.
• "Allow edits from maintainers" is checked. (See here for instructions on how to enable it.)
• My PR follows the style guide.
• I have assigned the correct reviewers to this PR (or will leave a
  comment with the phrase "@{{reviewer_username}} PTAL" if I don't have
  permissions to assign reviewers directly).

Proof that changes are correct

Proof that question admins can access the old contributor admin dashboard when feature flag is disabled/ can't access the new contributor admin dashboard when feature flag is enabled and question coordinators can access the new contributor admin dashboard when feature flag is enabled.

Screencast.from.03-11-23.11.08.04.AM.IST.webm

No console errors in new contributor admin dashboard and only languages assigned to the coordinator are shown in the dropdown.

Screencast.from.03-11-23.11.12.14.AM.IST.webm

Proof of changes on desktop with slow/throttled network

Proof of changes on mobile phone

Proof of changes in Arabic language

PR Pointers

• Never force push! If you do, your PR will be closed.
• To reply to reviewers, follow these instructions: https://github.com/oppia/oppia/wiki/Make-a-pull-request#step-5-address-review-comments-until-all-reviewers-approve
• Some e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.
• See the Code Owner's wiki page for what code owners will expect.

[seanlip]

@kshitij01042002 Could you please provide more detail in point 3 of the description and also in the proof of changes? Thanks.

[kshitij01042002]

Hi @seanlip I have updated the description PTAL. Thanks.

[vojtechjelinek]

Thanks! Just one nit.

[vojtechjelinek]

Suggested change

	if new_dashboard_enabled and (
	role_services
	.ACTION_ACCESS_NEW_CONTRIBUTOR_DASHBOARD_ADMIN_PAGE in (
	self.user.actions
	)):
	if new_dashboard_enabled and (
	role_services.ACTION_ACCESS_NEW_CONTRIBUTOR_DASHBOARD_ADMIN_PAGE
	in self.user.actions
	):

[seanlip]

@kshitij01042002 FYI the changes in #19108 might help fix the backend test failure in your PR. (See the description of that PR for details.)

[lkbhitesh07]

Thanks for the changes @kshitij01042002 LGTM for the code owner file.

[oppiabot]

Hi @kshitij01042002, this PR is ready to be merged. Please address any remaining comments prior to merging, and feel free to merge this PR once the CI checks pass and you're happy with it. Thanks!

[seanlip]

I am merging this to unbreak develop.