Project HashMap: Improve requirement clarity

[cyphersept]

Because

• This PR aims to improve clarity of the assignment instructions for Project: HashMap by decreasing wordiness and making implicit requirements explicit, so that students can more easily understand the complex project standards

This PR

• Added variables for load factor and capacity to explicit requirements
• Clarified expected behaviour for bucket growth
• Added link to previous lesson's section on collision handling referenced in the assignment
• Clarified expected outcomes in testing section
• Made terminology more consistent with itself and with previous lesson: "capacity" is now used only to describe the number of buckets in the hash map, "load levels" and "fullness" used only to describe what fraction of the HashMap's capacity is actually filled, and "load factor" is used for the maximum allowed load level before the buckets are grown.
• Some verbose sentences rewritten
• Some vague descriptions expanded
• Verbal "fluff" removed in lengthy sections
• Minor grammatical fixes

Issue

Related to #27682

Additional Information

Discord username: @phosphorflux

Pull Request Requirements

• I have thoroughly read and understand The Odin Project curriculum contributing guide
• The title of this PR follows the location of change: brief description of change format, e.g. Intro to HTML and CSS lesson: Fix link text
• The Because section summarizes the reason for this PR
• The This PR section has a bullet point list describing the changes in this PR
• If this PR addresses an open issue, it is linked in the Issue section
• If any lesson files are included in this PR, they have been previewed with the Markdown preview tool to ensure it is formatted correctly
• If any lesson files are included in this PR, they follow the Layout Style Guide

[JoshDevHub]

Nice work. Looks mostly good, just have one small nit and one small thing to discuss before I approve/merge. Let me know what you think.

[JoshDevHub]

Nice work. Just one more small change to get the Markdown linter to pass, and then I'll be good to merge.

Another thing: the Ruby course has this exact same project in it just with example code written in the Ruby language. Would you be comfortable making a new PR that makes these updates there as well? You shouldn't have to know any Ruby to do this, and if you had any questions, I'd be glad to help.

[cyphersept]

@JoshDevHub thanks for the catch, I fixed the linter issue. I went ahead and made the changes to the Ruby lesson on the newest commit after the lint fix because I think it makes more sense to keep the changes synced in the same PR. If you'd rather I open a new PR, please let me know.

[JoshDevHub]

Alright, looking good. And it's fine to have the Ruby stuff in this PR as well.

Just a couple small changes related to differences in Ruby and JS, but after those are good to go, I'll be glad to merge.

Thank you for making these changes. I think they make the project a lot better 🥇

[JoshDevHub]

Looks great. Thank you so much for putting in the work on this.