v2.1: Ensure that Rc in AccountInfo is not stored in an account (backport of #3471)

[mergify]

Problem

With direct mapping, AccountInfo should not be allowed to be stored in accounts; that includes the Rc<T> as well.

Summary of Changes

Fixes #

---

This is an automatic backport of pull request #3471 done by [Mergify](https://mergify.com).

[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.

[seanyoung]

This is some work that was missed in #3044
We need to ensure that AccountInfo fields are not in the input area.
Needed for direct mapping.

Cc @alessandrod

[t-nelson]

the direct mapping feature gate will be rekeyed as a result of this change to its logic, right?

this must be done before the next 2.1 release after the backport is merged