fix(curriculum): inconsistencies for code examples in cat photo app

[jdwilkin4]

Summary of changes

As I was helping campers on the forum, I noticed there were inconcentices and when we show code examples for new concepts and when we don't.

For example in step 8, we explan what a src attribute is and provide an example
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-html-by-building-a-cat-photo-app/step-8

But then in other places like step 14, we just tell them to add target attribute with _blank without a code example
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-html-by-building-a-cat-photo-app/step-14

However, this is popular post on the forum where campers don't know what to do and are just guessing at syntax
https://forum.freecodecamp.org/search?q=step%2014%20%23html-css%20after%3A2024-03-01%20cat%20photo%20app

Also, sometimes we have code examples inline like this
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-html-by-building-a-cat-photo-app/step-10

And then other times we don't.

IMO, we should always follow this format when it comes to introducing new concepts

1. teach the concept
2. show an example. Preferably in a code block.
3. give the directions on what to do in the project

This PR fixes the code example inconsistencies for new concepts and should help with the number of queries we get on the forum.

Checklist:

• I have read and followed the contribution guidelines.
• I have read and followed the how to open a pull request guide.
• My pull request targets the main branch of freeCodeCamp.
• I have tested these changes either locally on my machine, or GitPod.

[naomi-lgbt]

I'm going to challenge this and say new concepts do not all need an example. New syntax does.

The more text we add, the less likely campers are to read any of it. If we're showing an example for every new element or attribute, we're also removing the "think about how you add an attribute" process after we've already taught them how to add an attribute.

[naomi-lgbt]

Honestly, looking at some of these steps, the tests are so ancient that they're still using jQuery.

Before shoving more examples into the steps, I think I'd rather see the tests + hint text updated to better guide the campers in a granular way.

[jdwilkin4]

@naomi-lgbt

I pushed an update to remove some of the code examples.
And left comments for the others.

We could remove the remaining code examples steps where I left comments and see if updating the hint text and tests will work instead

[naomi-lgbt]

I think we can go with this, I'll circle back next week and overhaul the tests.

[a2937]

Looks Good To Me! 👍