Revise integration testing to focus on supertest API testing

[vegetabill]

/testing-and-tdd/integration-testing.md is quite a comprehensive lesson that is underestimated at 2 hours to go through. Also includes too much theory and too much long blocks. It is not skimmable.

Revise Motivation Section

Too long, please revise to be more concrete: "Helps insure your API's won;'t change in a way that breaks your browser app"

Drop mocking

Issue #1217 already created a mocking lesson

Remove postman section

We have no plans to use postman as an API testing framework as it's better for the participants to learn how to write automated API tests.

Promote the API tests using supertests example the primary focus

Integration testing in the context of web apps is usually synonymous with API testing.

Move the "Interlude: Testing APIs with supertest" section to be the main content of this lesson. Revise all the other bullet points sections to match. This may in effect mean mostly rewriting this entire lesson, but try to reuse what you like in the existing content.

For FAQs on how to contribute, see: https://github.com/Techtonica/curriculum/blob/main/CONTRIBUTING.md

[vegetabill]

Related to #1215

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[alodahl]

I don't know if I agree with this bot. As this isn't a typical industry backlog, neglected doesn't equal worthless. If we don't need it anymore, we should close it intentionally.

[vegetabill]

I'll review and split this one up.

[vegetabill]

Seems related to #1215

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[alodahl]

@vegetabill I see you marked this one as "Before program begins". How do you feel about it? Should we open this to volunteers?

[vegetabill]

I think I missed that when prioritizing. The current schedule has this occurring at the end of week 7: https://github.com/Techtonica/curriculum#week-7---databases

So I'll move it to the correct milestone.

[alodahl]

Just to double-check, this work makes #961 unnecessary, right? If so, can you please close it?

[alodahl]

will not use file as-is now that we've moved to Jest testing.