Add upgrade_and_call

[andrew-fleming]

Fixes #694.

This PR proposes to add upgrade_and_call to UpgradeableComponent's InternalImpl. This PR also proposes to add IUpgradeAndCall interface which includes both upgrade and upgrade_and_call.

PR Checklist

• Tests
• Documentation
• Added entry to CHANGELOG.md
• Tried the feature on a public network
  • Addy on sepolia: https://sepolia.starkscan.co/contract/0x06e482b32240a783cdf69e658f31179575815734d1392a6b6f05a8d5b86aaec7#overview
  • upgrade_and_call to new selector (set_value2) in upgraded context: https://sepolia.starkscan.co/call/0x03ecdb12d63c133ded1bb2b85a9650aaf2c90e6dd6cb460aa8cf651fb3b73894_1_1

[ericnordelo]

Looking good Andrew. Left some comments.

[immrsd]

Good job, Andrew!
I've left a couple of comments

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.53%. Comparing base (c5cd715) to head (d3fb1df).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1148      +/-   ##
==========================================
+ Coverage   91.51%   91.53%   +0.02%     
==========================================
  Files          46       46              
  Lines        1178     1182       +4     
==========================================
+ Hits         1078     1082       +4     
  Misses        100      100              

Files with missing lines	Coverage Δ
packages/upgrades/src/upgradeable.cairo	100.00% <100.00%> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c5cd715...d3fb1df. Read the comment docs.

[immrsd]

Left a couple of minor suggestions. Apart from that, I think we are ready to go

[immrsd]

Let's not forget to add a reason or un-ignore the test

[ericnordelo]

LGTM! Let's just add the reason to the ignored tests, and I think we can merge this and fix the test later when we get more information about the test env issue since we already tested it on testnet.