Additional checks for Travis

[daemontus]

In this PR, we add extra verification steps to the Travis CI script. Specifically:

1. Treat warnings as errors. While sometimes acceptable, warnings should be generally avoided.
2. Check cargo formatting. Ensure project follows standard code style enforced by cargo.
3. Use clippy (rust lint tool) to verify other coding practices, line unnecessary if or return statements or simple performance anti-patterns.