[5][10] UX to allow proposals - don't simply disable "submit" buttons everywhere

Even when an account has no privilege to do some changes when browsing another account, or can't do certain operations due to no fee or etc, should be **possible to create proposals**, which is an important feature.

If the buttons are simply disabled, then no action can be done.

Perhaps need UX.

The issue does not name files, tests, or entry points. Start by tracing the submit buttons used for operations affected by account privileges, missing fees, or browsing another account, then determine how proposal creation should remain available. Done means the relevant operations can create proposals instead of being universally disabled, with the UX behavior agreed and covered by the project’s tests.

Written by the indexing model from the issue text.