v1.0.2

Give hubs and configs a traffic ceiling

A quota says how much may move, which direction counts -- download only,
upload only, or both -- and nothing else; the amount is entered in MB, GB or
TB and stored in bytes. Both a Virtual Hub and one user config can carry one,
independently.

Usage is a running total advanced from SoftEther's own cumulative counters
rather than a query over the sample tables, and that is deliberate: a ceiling
has to survive the retention window pruning the samples it was counting, and
it has to survive the VPN server restarting and zeroing its counters
mid-cycle. The last reading each quota was advanced to makes the arithmetic
idempotent, so the traffic sampler can donate the counters it already read for
free while enforcement keeps its own faster clock -- seconds, not minutes,
because a ceiling that bites late is a ceiling that leaked.

At the limit a config has policy:Access denied and its live sessions cut; a
hub is taken offline. Both are SoftEther's own switch for "this may not carry
traffic", and what was there before the block is kept so that raising the
limit, resetting the counter, disabling the quota or deleting it puts the
subject back exactly as it was found -- never at an assumed default. A hub
that was already offline when the quota bit stays offline.

The editor sits on the user page and the hub settings tab; the meter also
rides both user tables, as a sortable column, so a spent config is visible
without opening it.