feat: Add UpdateAdmin and ClearAdmin constructors in the Remote

[jawoznia]

No description provided.

[codecov]

Codecov Report

Attention: Patch coverage is 70.37037% with 8 lines in your changes missing coverage. Please review.

Project coverage is 72.18%. Comparing base (2da70e6) to head (6fb6049).
Report is 3 commits behind head on feat/replies.

Files with missing lines	Patch %	Lines
sylvia/tests/remote.rs	63.63%	8 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           feat/replies     #438      +/-   ##
================================================
- Coverage         72.20%   72.18%   -0.02%     
================================================
  Files                56       56              
  Lines              3457     3484      +27     
================================================
+ Hits               2496     2515      +19     
- Misses              961      969       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[uint]

LGTM! I only wonder if doc comments would be useful with these new pub methods

[hashedone]

One comment about API improvement.

[kulikthebird]

I like this change, it's nice to have those extra methods in the Remote implementation. The only thing I spend more time was checking the remote.rs file with tests. I realized it is more complicated than it can be. I know it's not directly related to this PR, but we can do a nice improvement with low cost:

1. unsigned_contract and signed_contract are pretty much the same - let's remove the code duplication and make a single Counter contract generic over the counter type. We can then add type SignedContract = Counter<i32>; type UnsignedContract = Counter<u32>;.
2. Names signed and unsigned reminds me of signing something with some cryptographic tool, when in this context it means i32 and u32. Let's change it to CounterI32/CounterU32 or ContractI32/ContractU32 instead.
3. ContractStorage is a dead code - to be removed.
4. Remove the #[entry_points(generics<i32>)] - we don't need it in the test scenarios. Moreover it might be misleading for other devs:

• it's only i32, but we can support many other types - better way would be to add feature flags for the contracts to choose between entry points types,
• it gives a hint that it always should be present with sylvia contracts - it doesn't have to.

[kulikthebird]

Let's create a new setup function for the admin scenarios

[jawoznia]

I agree it could be simplified

2. Names `signed` and `unsigned` reminds me of signing something with some cryptographic tool, when in this context it means `i32` and `u32`. Let's change it to `CounterI32`/`CounterU32` or `ContractI32`/`ContractU32` instead.

I can see that. Let's change it later.

3. `ContractStorage` is a dead code - to be removed.

This is intentional. There was a bug where it was impossible to store Remote in custom storage types. A comment explaining this would be very much in place.

4. Remove the `#[entry_points(generics<i32>)]` - we don't need it in the test scenarios. Moreover it might be misleading for other devs:

It provides the coverage though.
I would prefer to move all the bloated examples to the tests and make them act as the coverage.
The examples should be refactored to provide simple single feature showcases.