[3.2] more compiler warnings cleanup

[linh2931]

Partially resolve #254

After this PR, only 4 warnings remain in submodules abieos and libfc/libraries/ff/libff.

Most of the changes are straightforward. The following two need to be noted.

1. For #warning directives in wasm_tests.cpp and api_tests.cpp, I created issues for them Use github issue instead of #warning directive in wasm_tests.cpp #259 and Use github issue instead of #warning directives in api_tests.cpp #260. I think this is a better way to handle TODOs. Leaving them in #warning will not get them to be done. I kept them as comments for easier identification if we decide to work on them.
2. To resolve the warning in chain_plugin.cpp, I need to introduce a new macro FC_LOG_AND_DROP_NO_INTERPROCESS_BAD_ALLOC. The warning was

In file included from /home/lh/work/leap-main/libraries/chain/include/eosio/chain/          exceptions.hpp:3,
                 from /home/lh/work/leap-main/libraries/chain/include/eosio/chain/asset.hpp:2,
                 from /home/lh/work/leap-main/plugins/chain_plugin/include/eosio/           chain_plugin/chain_plugin.hpp:3,
                 from /home/lh/work/leap-main/plugins/chain_plugin/chain_plugin.cpp:1:
/home/lh/work/leap-main/plugins/chain_plugin/chain_plugin.cpp: In member function ‘void     eosio::chain_apis::read_write::push_block(eosio::chain_apis::read_write::                   push_block_params&&, eosio::chain_apis::next_function<eosio::chain_apis::empty>)’:
/home/lh/work/leap-main/libraries/libfc/include/fc/exception/exception.hpp:481:4: warning:  exception of type ‘boost::interprocess::bad_alloc’ will be caught
  481 |    catch( const boost::interprocess::bad_alloc& ) {\
      |    ^~~~~
/home/lh/work/leap-main/libraries/libfc/include/fc/exception/exception.hpp:481:4: note: in  definition of macro ‘FC_LOG_AND_DROP’
  481 |    catch( const boost::interprocess::bad_alloc& ) {\
      |    ^~~~~
/home/lh/work/leap-main/plugins/chain_plugin/chain_plugin.cpp:2169:6: warning:    by        earlier handler for ‘boost::interprocess::bad_alloc’
 2169 |    } catch ( boost::interprocess::bad_alloc& ) {
      |      ^~~~~

[heifner]

I don't think we should make any of these changes to elliptic_webauthn.cpp. I'm concerned there is a potential consensus difference here.

[spoonincode]

We can also silence the warning with __builtin_unreachable at the end of the function, I believe. As-is, if it makes it to the end of the function it's pretty much UB anyways 🤷

[linh2931]

Thanks. I will do an elog and then call __builtin_unreachable at the end of the function.