Add option for PFDs to not follow non-interactive defaults

[evan-forbes]

There are rollup constructions where it is not necessary to to know the commitment to the block data ahead of time. For example a rollup that

• uses deferred execution
• executes immediately but simply waits to include the header in the next celestia block
• only includes block data in celestia and distributes the header via some other means
  or
• as stated in the specs, one that interacts with the block producer

This would allow for a more efficient use a blockspace, and often a cheaper fee provided submitter's of PFDs end up paying for some portion of padding #431

[evan-forbes]

closing as this issue does not align with the implementation of non-interactive defaults at this time. There doesn't need to be a specific option, as wrapped txs and message inclusion handle this for us.

[evan-forbes]

it also misses the point of non-interactive defaults that I somehow manage to keep forgetting. They have nothing to do with rollup execution, just message inclusion