fix(learn): Improve tests for the Nest an Anchor Element within a Paragraph challenge

[RandellDawson]

Checklist:

• I have read freeCodeCamp's contribution guidelines.
• My pull request has a descriptive title (not a vague title like Update index.md)
• My pull request targets the main branch of freeCodeCamp.
• All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

I created this PR to address a recurring confusion I see in the Nest an Anchor Element within a Paragraph challenge. This is the first challenge where the user is introduced to the concept of nesting an existing element into a newly created element. So many times, a user ends up creating another anchor element instead of just using the existing anchor element. Creating a new anchor element without the exact attributes/text of the original can lead to problems such as the one in this forum topic.

This PR aims to better guide the user into writing the correct code. This is similar to the approach we are taking in the v7 curriculum.

[gitpod-io]

[naomi-lgbt]

Looks good to me.

[raisedadead]

I disagree. (kidding just testing out the auto merge, randy is awesome)

[raisedadead]

@moT01 can you approve this change. I believe the merge should be held in place due to my change request review.

[moT01]

LGTM 🎉

[raisedadead]

Bazinga! That works

[raisedadead]

@RandellDawson go ahead and dismiss my review. It should merge the PR.

[RandellDawson]

@raisedadead Cool, so not until you either dismiss your requested change or approve it, will anything else happen?

[raisedadead]

Cool, so not until you either dismiss your requested change or approve it, will anything else happen?

That is correct. Why don't you go ahead and try dismissing my review?

Testing dismissal of test review

[naomi-lgbt]

Woah that's neat.

[RandellDawson]

I just hope this does not get abused. For instance, if there was a hold out mod that was requesting changes and two other mods approve and just decide to dismiss the other mod's requested changes. It could be a non-issue.

[ShaunSHamilton]

I do not see myself making all that much use of this auto-merge feature, because I often edit the commit message.

[naomi-lgbt]

@ShaunSHamilton for what it is worth, the default commit message would be the title of the pull request.

[raisedadead]

because I often edit the commit message.

You will be able to edit the message prior commit. Everything works as usual (the only advantage is you skip the wait for a CI to pass, which could be helpful if we mandated the Cypress tests to be required)

Screenshot of editing commit message prior enabling auto merge: