Remove tweet from historical alert SQL generation

## Description

Remove the archived `tweet` field from historical alert SQL/data generation.

The `tweet` column is planned for removal from the historical alert tables, but AlertTools still writes it through `tabela_historico()` and `write_alerta()`.

## Required work

- remove `tweet` from historical alert output generated by `tabela_historico()`;
- remove `tweet` from `write_alerta()` SQL for dengue, chikungunya and zika historical alert tables;
- keep the generated SQL compatible with:
- `Municipio.Historico_alerta`;
- `Municipio.Historico_alerta_chik`;
- `Municipio.Historico_alerta_zika`;
- review exported `getTweet()` and mark it deprecated, archived or unused if it is no longer part of active workflows;
- add tests for tweet-free generated data frames and SQL;
- confirm AlertaDengueAnalise can run with the updated AlertTools.

## Out of scope

- dropping the database column;
- changing unrelated historical alert fields;
- changing AlertaDengue API behavior;
- changing production data.

## Acceptance criteria

- `tabela_historico()` no longer requires or emits `tweet`;
- `write_alerta()` no longer writes `tweet`;
- generated SQL does not reference the `tweet` column;
- tests cover dengue, chikungunya and zika SQL generation;
- AlertaDengueAnalise integration path is verified;
- database migration in AlertaDengue is unblocked.