add bulk transactions on a drawdown

We got a change request to implement a bulk upload of budget expenditures, that would be stored on a ipfs file to be categorized later. To solve this new issue we need to add / implement a medium change on the drawdown.

[x] First wee need to update the data type of files in the table.
[x] Then add CRUD actions for the drawdown table new value.

[x] Update drawdown_table variable url_information -> extended_url_information

TABLE drawdown_table                                                                         
{                                                                                            
uint64_t drawdown_id;                                                                      
uint64_t drawdown_number;              
std::string type_str;                                                                      
eosio::name type;                                                                          
eosio::asset total_amount;                                                                 
vector<common::types::extended_url_information> files; /*  TODO update this to extended version*/   
uint64_t state;                                       
uint64_t open_date;                                                                        
uint64_t close_date;                                                                       
eosio::name creator;                                                                       

uint64_t primary_key() const { return drawdown_id; }                                       
uint64_t by_type() const { return type.value; }                                            
uint64_t by_state() const { return state; }                                                
uint64_t by_date() const { return open_date; }                                             
uint128_t by_type_creation() const { return (uint128_t(type.value) << 64) + (open_date); } 
uint128_t by_close_type() const { return (uint128_t(close_date) << 64) + (type.value); }   
};

[x] We need to change file to an extended files version that includes, filename, address and description. The new data type should looks something like this
[x] Change the structure to support multiple files in case a single file exceeds 100 mb

struct extended_url_information
    { // ! store budget expenditures
      std::string filename;
      std::string address;
      std::string description;
      uint64_t date;
      eosio::asset amount;
    }; 

struct extended_url_information_param
    { // ! store budget expenditures
      std::string filename;
      std::string address;
      std::string description;
      uint64_t date;
      eosio::asset amount;
      bool add_file; // true = add, false = remove
    };

[x] The actions that would be added on transactions smart contract should be something like this

bulktransact(const eosio::name &actor, const uint64_t &project_id,  const uint64_t &drawdown_id, vector<extended_url_information_param> transactions)

[x] Create a function on base_drawdown called 'edit()'.
[x] Add previous function for the childs as 'edit_impl'.
[x] it would call a new function on base_drawdown called edit() (and edit_impl for the child's) This function basically would add or delete a file in the files vector on the drawdown table. The flow must be similar to update() because we still managing transactions of budget expenditures, and
[x] only builder can add/delete files (atm)
[x] add validations
[x] Test workflow
[x] Create Unit tests

we still need to define the way of how the transactions would be added on the respective budget expenditure account, but lets not focus on that part yet.

hashed-io / proxy-financial-smart-contracts

add bulk transactions on a drawdown #27