notify_changed_objects should rethrow when caught a plugin_exception

[abitmore]

Bug Description

plugin_exception is designed to be handled when pushing a block:

bitshares-core/libraries/chain/include/graphene/chain/exceptions.hpp

Lines 97 to 101 in d04c62a

	catch( const graphene::chain::plugin_exception& e ) \
	{ \
	elog( "Caught plugin exception: ${e}", ("e", e.to_detail_string() ) ); \
	throw; \
	} \

Functions like notify_applied_block() and etc behavior correctly

bitshares-core/libraries/chain/db_notify.cpp

Lines 446 to 449 in d04c62a

	void database::notify_applied_block( const signed_block& block )
	{
	GRAPHENE_TRY_NOTIFY( applied_block, block )
	}

But notify_changed_objects() silently captures and drops the exception:

bitshares-core/libraries/chain/db_notify.cpp

Line 512 in d04c62a

} FC_CAPTURE_AND_LOG( (0) ) }

Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.

• API (the application programming interface)
• Build (the build process or something prior to compiled code)
• CLI (the command line wallet)
• Deployment (the deployment process after building such as Docker, Travis, etc.)
• DEX (the Decentralized EXchange, market engine, etc.)
• P2P (the peer-to-peer network for transaction/block propagation)
• Performance (system or user efficiency, etc.)
• Protocol (the blockchain logic, consensus, validation, etc.)
• Security (the security of system or user data, etc.)
• UX (the User Experience)
• Other (please add below)

CORE TEAM TASK LIST

• Evaluate / Prioritize Bug Report
• Refine User Stories / Requirements
• Define Test Cases
• Design / Develop Solution
• Perform QA/Testing
• Update Documentation

[abitmore]

Fixed by #2242.