Feature - Remove loader v4 instruction deploy from source

[Lichtso]

Problem

The deploy from source instruction is unnecessary as its use case is covered by the copy instruction.

Summary of Changes

The CLI now sends the sequence:

• Either create or retract program account
• Set length of program account
• Copy from buffer account
• Deploy program account
• Set length of buffer account to zero, effectively closing it and retrieving its funds

Feature Gate Issue: #78

[mergify]

The Firedancer team maintains a line-for-line reimplementation of the
native programs, and until native programs are moved to BPF, those
implementations must exactly match their Agave counterparts.
If this PR represents a change to a native program implementation (not
tests), please include a reviewer from the Firedancer team. And please
keep refactors to a minimum.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 41.53846% with 38 lines in your changes missing coverage. Please review.

Project coverage is 82.8%. Comparing base (9f99b75) to head (343c470).
Report is 33 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5968   +/-   ##
=======================================
  Coverage    82.8%    82.8%           
=======================================
  Files         830      830           
  Lines      377204   377143   -61     
=======================================
- Hits       312481   312474    -7     
+ Misses      64723    64669   -54     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.