feat: optimize build

[chadoh]

stellar-cli v27 includes --optimize by default.

We just need to include additional-libs in order to enable it.

This makes the build for stellar-scaffold-cli much bigger!

Alternatives

Rather than embedding stellar-cli, we could shell out to it. This would require a more significant re-architecture. Is it worth it, before shipping this feature? (Ideally, we should do some more data-driven comparison of the current approach vs status quo to understand the increased build/install time of stellar-scaffold-cli to see if we
think it's worth going with the simpler-to-ship approach for now.)

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: cargo openssl is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/reqwest@0.12.24 → cargo/openssl@0.10.81 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/openssl@0.10.81. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[willemneal]

Makes sense to me and we can shell out later if there are issues and in general move away from reimplementing the stellar cli