Add weights/runtime mock/benchmarking to vesting-manager pallet

remove_vesting_schedule extrinsic uses hardcoded weighs

#[pallet::weight(10_000_000)]

#[pallet::call]
	impl<T: Config> Pallet<T> {
        #[pallet::call_index(0)]
        #[pallet::weight(10_000_000)]
        pub fn remove_vesting_schedule(
	        origin: OriginFor<T>,
	        who: AccountIdLookupOf<T>,
	        schedule_index: u32,
        ) -> DispatchResultWithPostInfo {
	        ensure_root(origin)?;
	        let who = T::Lookup::lookup(who)?;
	        T::VestingSchedule::remove_vesting_schedule(&who, schedule_index)?;
        
	        Self::deposit_event(Event::VestingScheduleRemoved { who, schedule_index });
        
	        // waive the fee
	        Ok(Pays::No.into())
        }
}

To automatically regenerate weight for extrinsic need :

• add mock.rs
• add benchmarking.rs
• add pallet to runtime
• build runtime with benchmarking feature
• run ./target/release/spacewalk-standalone benchmark pallet to regenerate weights.

Start at the vesting-manager pallet's remove_vesting_schedule extrinsic and inspect how its hardcoded weight is represented. Read the pallet's mock.rs and benchmarking.rs along with its runtime integration, then build with the benchmarking feature and run ./target/release/spacewalk-standalone benchmark pallet. Done means the extrinsic uses generated benchmark-based weights instead of the hardcoded 10_000_000 value.