updated table prices to what we agreed

Eventually it might be worth make this more generic and configurable.  In the past, the way we've done table pricing has changed a lot, so there hasn't been a single approach that we could just make configurable.  But we seem to be doing basically the same thing year to year now, so we could probably make it more configurable, something like

```
[table_prices]
1 = 125
2 = 175
3 = 250
4 = 350
```

Then dynamically construct the ``TABLE_PRICES`` config option based on that.  Or something like that.  For now this is fine.