create single 'Get Token' button for all local repos

[ShaiahWren]

Issue: https://issues.redhat.com/browse/AAH-903

Assignment:

1. Only one "Get Token" button for the list view in the header. Only when 'local' repos tab is selected
2. Button does not redirect to a new tab

Before:

After:

[ZitaNemeckova]

@ShaiahWren This should be in BaseHeader param pageControls. See

ansible-hub-ui/src/containers/group-management/group-detail.tsx

Lines 200 to 215 in 2e1946f

	<BaseHeader
	title={
	editPermissions && params.tab == 'permissions'
	? t`Edit group permissions`
	: group.name
	}
	breadcrumbs={
	<Breadcrumbs
	links={[
	{ url: Paths.groupList, name: t`Groups` },
	{ name: group.name },
	]}
	/>
	}
	pageControls={this.renderControls()}
	>

for reference.

After moving it there shouldn't be any need for new CSS and it should consistent with similar pages.

[awcrosby]

(adding this to a few recently updated PRs…) We need CI in this repo that enforces this, but for now please:

• Add a line to at least one of your commits that says Issue: AAH-#### (in the future it is best to be the first commit as it gets included in the initial PR description by default)
• Ensure when merging that the Issue: AAH-#### is part of commit message via the “Squash ‘n’ Merge” description

[ZitaNemeckova]

LGTM 👍 Don't forget to fix a commit according to Andrew's comment before merging :)

[ShaiahWren]

Issue: AAH-903

[patchback]

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

❌ Failed to cleanly apply 0fad2f9 on top of patchback/backports/stable-4.4/0fad2f9766807b5c55cd9442e5dd3ac69152a9e7/pr-1257

Backporting merged PR #1257 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/ansible-hub-ui.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/0fad2f9766807b5c55cd9442e5dd3ac69152a9e7/pr-1257 upstream/stable-4.4

4. Now, cherry-pick PR create single 'Get Token' button for all local repos #1257 contents into that branch:

   $ git cherry-pick -x 0fad2f9766807b5c55cd9442e5dd3ac69152a9e7

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

   $ git cherry-pick -m1 -x 0fad2f9766807b5c55cd9442e5dd3ac69152a9e7

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR create single 'Get Token' button for all local repos #1257 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4.4/0fad2f9766807b5c55cd9442e5dd3ac69152a9e7/pr-1257

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.

[himdel]

(backport failed because of a conflict with (missing) #1259 , backporting that one first => #1371)

[patchback]

Backport to stable-4.4: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-4.4/0fad2f9766807b5c55cd9442e5dd3ac69152a9e7/pr-1257

Backported as #1375

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