doc: guide for extending a deployed contract's Wasm code TTL

[Mystic-Nayy]

resolves #618

[briwylde08]

Thank you for your submission @Gift-Naomi! We'll get this assigned and reviewed and let you know any feedback!

[Mystic-Nayy]

@briwylde08 Alright, I will be waiting.

[ElliotFriend]

Hi, @Gift-Naomi! Thanks for participating in our docs bounty!

I'm a little unsure how to start reviewing your contribution. There's a few things you'll need to address before we really can get into reviewing this.

1. You're replaced this existing guide, but we're looking to have a new guide created instead. Probably a new file in the /docs/build/guides/archival directory would fit best.
2. It looks like you're writing in a way that could generically apply to several blockchains. I see references to substrate, polkadot, ink, etc. but no mention of Stellar and/or Soroban. We're wanting these guides to be written in a that's targeted and specific to Stellar.
3. Based on the example contract you've provided here, it seems like you might be misunderstanding some of what we mean when we say TTL. Check out the State Archival docs to get a better handle on it. Particularly, the terms and semantics section might be useful for a quick overview.

Do those points make sense? If you have any questions, I'm more than happy to help get things unblocked for you.

Thanks again!

[Mystic-Nayy]

@ElliotFriend
This guide includes both a code walkthrough and written explanations to help users understand how to extend the TTL of a deployed Wasm contract on Stellar. Let me know if you need any adjustments!

[Myestery]

@Gift-Naomi please take a look at https://github.com/stellar/soroban-examples/tree/main/ttl/src
TTL logic is exemplified there

[Myestery]

Here too
https://developers.stellar.org/docs/build/guides/archival/test-ttl-extension

[briwylde08]

Hi there @Gift-Naomi - we appreciate your effort and participation in the bounty. However, this doesn't quite solve for the ask in the corresponding bounty issue. We are looking for code examples for the task instead of CLI work and the contract code provided in this PR doesn't extend the contract's TTL. Again, we do appreciate the time and effort put into the bounty. If you have any questions, don't hesitate to ask.

All the best,
Bri