Determine proper way to manage sizes/options

[spotlightishere]

We currently have the following hardcoded in many areas:

food-server/responses.py

Lines 95 to 113 in 9753172

	"optionList": {
	"testing": {
	"info": "Here so everything works!",
	"code": 1,
	"type": 1,
	"name": "WiiLink",
	"list": {
	"item_one": {
	"name": "Item One",
	"menuCode": 1,
	"itemCode": 1,
	"image": 1,
	"isSoldout": 0,
	"info": "Here so everything works!",
	"price": "5.99",
	}
	},
	}
	},

Similarly, for sizes:

food-server/responses.py

Lines 241 to 252 in 9753172

	# TODO: sizeList should be populated from actual data, instead of hardcoded.
	# For now, we will populate sizes with the generic size "Regular",
	# using the item's existing, configured properties.
	return {
	"itemCode": item.item_code,
	"name": item.name,
	"price": item.price,
	"info": item.description,
	"size": "Regular",
	"image": item.item_code,
	"isSoldout": 0,
	}

We need to make these backed by the database.

[Auxy6858]

Is the database in question already set up or not?