timeline.js: loadMoreStatuses() now sends query with ack_state=acked instead of ack_state=any. Current version of loadMoreStatuses() won't ack loaded statuses, so it should not load unacked statuses anyway.

Querying with ack_state=any can cause loading duplicate statuses at least in the following two cases.

case A.

1. At initialization.
2. In loadInit(), loadUnackedStatues() yields no unacked statuses. ack done.
3. Then, some unacked statuses are added.
4. Then, loadInit() calls loadMoreStatuses(). Because there is no status in the container,
   it queries with no max_id and ack_state=any.
   This yields the unacked statuses added at step 3, but they are not acked.
5. Initialization completes.
6. New button indicates unacked statuses at step 3 are there.
   Hitting the button loads them again, leading to duplicate statuses.

case B.

1. No status in timeline at initialization. The container is empty.
2. New unacked statuses are added. New button indicates their presence.
3. Hit More button. It queries with no max_id and ack_state=any.
   So the unacked statuses added at step 2 are loaded, but they are not acked.
4. Hit New button. It loads duplicate statuses.
timeline.tt: message banner is on the right side of the page, because controls are aligned on that side, too.
timeline.js: StatusContainer: possible minor error fixed in _adjustCursor().
timeline.js: always try to set the cursor after loading statuses if the cursor is not set yet.