Board Initialization: Architecture-specific initialization vs Custom board late initialization

When putting an application on ENTRYPOINT instead of launching it manually through nsh, some driver initialization is missing.

This is explained in the faq. https://nuttx.apache.org/docs/latest/faq/index.html#why-after-putting-my-application-on-entrypoint-it-stops-to-work

Is there a drawback to replace `CONFIG_NSH_ARCHINIT=y` by `CONFIG_BOARD_LATE_INITIALIZE=y` in the boards defconfig ?
Is `CONFIG_NSH_ARCHINIT` useful compared to `CONFIG_BOARD_LATE_INITIALIZE` ?

This way new users won't have to figure out why their application works when launching from nsh and doesn't when launching as ENTRYPOINT.

Start with the FAQ section linked in the issue and inspect the boards' defconfig files for CONFIG_NSH_ARCHINIT and CONFIG_BOARD_LATE_INITIALIZE. Compare how ENTRYPOINT and nsh affect driver initialization, then determine whether replacing the setting is safe and what documentation or configuration changes would be needed.

Written by the indexing model from the issue text.