Details

Can now differentiate between an expansion pack beacon and a normal beacon
If an expansion pack beacon is detected, check Firebase to see if a new pack is available for this location (using version number). If a new pack is available or if the pack does not exist on the user's device (e.g. it is their first time passing that location) then a second request is made to fetch the contents of the expansion pack and then put it into the local database
The following workflow now works:
- Walk past expansion pack beacon which has been added to the Firebase and has a corresponding expansion pack file added to the other GitHub repo here
- If the expansion pack relating to this beacon has not been downloaded before, or if it is out of date, the system will automatically download the latest expansion pack into local storage
- When you walk past a beacon included in the expansion pack, the enriched content is provided to the user

Screenshots/GIF (if appropriate)

At 00:07 the beacon is detected with its NMW code (no enriched content available)
Sometime between 00:20 and 00:55 an expansion pack beacon is detected which includes enriched content for the previous beacon
At 00:57, the beacon is detected again but this time with the enriched content since it has been downloaded

No actual front end changes were made here

Closes #50, #51 #52