[basic.stc.dynamic.general], [func.wrap.func], [any.class.general] "Dynamically allocated" is not defined

In a number of normative paragraphs, we use the term "dynamically allocated", but it is never defined:

• "Objects can be created dynamically" ([basic.stc.dynamic.general] p1)
• "Implementations should avoid the use of dynamically allocated memory for small callable objects"
  • ([func.wrap.func.con] p5)
  • ([func.wrap.func.con] p7)
  • ([func.wrap.func.con] p15)
• "Implementations should avoid the use of dynamically allocated memory for a small contained value"
  • ([func.wrap.move.class] p2)
  • ([func.wrap.copy.class] p2)
  • ([any.class.general] p3)

We could generally fix this problem by talking about

objects with dynamic storage duration

... instead of

dynamically allocated objects

... or by talking about allocation functions.

Implementations should avoid the use of
-dynamically allocated memory
+storage obtained through allocation functions
for a small contained value.

Also, I'm not too hyped about the recommended practice being copied and pasted into three separate std::function constructors, but it's not the end of the world.

Note: I've noticed this issue when working on https://github.com/cplusplus/draft/pull/7260.

Start with [basic.stc.dynamic.general] p1 and the referenced [func.wrap.func.con], [func.wrap.move.class], [func.wrap.copy.class], and [any.class.general] paragraphs. Compare the uses of “dynamically allocated” with the suggested wording about dynamic storage duration or allocation functions. Done means the affected normative paragraphs use a defined, consistent term and the duplicated std::function recommendations have been considered.