Lumbridge immersion update

What have you done in this MR?

• added sound to shearing sheep
• added sound to failing to shear the penguin sheep
• added sound to picking up field items(wheat,potato...etc)
• added 3 missing chicken(1017) spawns to farmer freds farm Freds Chickens Video Source
• removed 1 incorrect chicken(41) spawn from farmer freds farm

Sheep: There were many missing sheep spawns Sheep Video Source

Sheep Before-Sheep After

• added 1 missing sheep(43) spawns at farmer freds farm
• added 2 missing sheep(1765) spawns at farmer freds farm
• added 2 missing sheep(5156) spawns at farmer freds farm
• added 2 missing sheep(5157) spawns at farmer freds farm
• added 2 missing sheep(5160) spawns at farmer freds farm
• added 1 missing ram(3673) spawn at farmer freds farm
• added all combat sounds to ram(5168,3673)

Lumbridge castle southwest corner: Giant rat spawns were incorrect and some npcs were missing Lumbridge Southwest Video Source

Castle SW Before-Castle SW After

• added 1 missing mugger(175) spawn behind lumbridge by logs
• added all combat sounds to mugger(175)
• added 2 missing sheep(42) spawns behind lumbridge by logs
• removed 6 incorrect giant rat(86) spawns at southwest corner of lumbridge castle
• added 2 giant rat (86) spawns at southwest corner of lumbridge castle
• added 1 giant rat (4942) spawn at southwest corner of lumbridge castle
• added 10 missing rat(47) spawn at southwest corner of lumbridge castle

Goblins: The goblins west of lumbridge castle were all the wrong type Goblin Source Video1- Goblin Source Video2- Goblin Source Video3- Goblin Source Video4

East Before- East After - West Before- West After

• removed 24 incorrect goblin spawn(all 3267,3264) between lumbridge and draynor
• added 3 goblin(2278) spawn between lumbridge and draynor to east section
• added 1 goblin(1772) spawn between lumbridge and draynor to east section
• added 1 goblin(1770) spawn between lumbridge and draynor to east section
• added 2 goblin(1771) spawn between lumbridge and draynor to east section
• added 3 goblin(2279) spawn between lumbridge and draynor to east section
• added 2 goblin(2281) spawn between lumbridge and draynor to east section
• added 1 goblin(2278) spawn between lumbridge and draynor to west section
• added 1 goblin(1772) spawn between lumbridge and draynor to west section
• added 1 goblin(1770) spawn between lumbridge and draynor to west section
• added 1 goblin(1771) spawn between lumbridge and draynor to west section
• added 1 goblin(2279) spawn between lumbridge and draynor to west section
• added 1 goblin(2280) spawn between lumbridge and draynor to west section
• added 2 goblin(2279) spawn between lumbridge and draynor to north section
• added 1 goblin(1770) spawn between lumbridge and draynor to north section
• added 1 goblin(1771) spawn between lumbridge and draynor to north section
• added 1 goblin(2278) spawn between lumbridge and draynor to north section

Giant spiders: some spawns were missing and existing ones were in the wrong location Giant Spiders Video Source

Ham Trapdoor Before- Ham Trapdoor After- Well Area Before- Well Area After

• removed 2 incorrect giant spider(59) spawns at ham trapdoor
• added 5 giant spider(59) spawn at ham trapdoor
• removed 3 incorrect giant spider(59) spawns around well
• added 3 giant spider(59) spawn at well
• removed 1 incorrect spider(59) at giant rats spawn near lumbridge by logs
• added 1 missing giant spider(59)spawn next to tree patch

Are there any tricky things testers should keep an eye out for?

• No

• Yes, as follows:

• I have tested these changes thoroughly.

• This requires extra testing due to changes to architecture or other similarly risky changes.

• I used the Thanos Tool for any JSON edits where possible, and have attached screenshots of any changes.

• I acknowledge that this contribution will be released under the AGPL license.

*** NOTE: If Gitlab complains about pipelines stating that you need to "Validate your Gitlab account" there is no need to worry. You do not have to do this and it is only occurring because OUR pipeline tried to run on your fork. While it's preferred that you do validate your account, you can safely ignore/dismiss this message from Gitlab. ***