Allow killing multiple specific sessions
Syntax changes
Add support for jobs -k ranges
Add support for sessions -d ranges
Merge pull request #1 from wvu-r7/pr/4063

Add support for jobs -k ranges from @wvu
Change killing back to stopping

Got a little excited with the copypasta, I guess.
Merge pull request #2 from wvu-r7/pr/4063

Change killing back to stopping
- Added range support to sessions -c and sessions -s
- Added check for un-detach-able sessions
- Added back the check for session.interactive? when detaching sessions
- Collapse build_jobs_array and build_sessions_array to build_range_array
- Added check for empty or invalid parameters to detach and kill [session | job]
- Reworked session id sanity check around line 1660
- RuboCop/Style guide change: Array.new -> []
- Misc RuboCop/Style guide spacing changes
added mssql_escalate_executeas module
fixed code comment
comment fix-sorry
modernizes & DRYs session/job ranges
Merge pull request #3 from kernelsmith/landing/4063-DRYer

modernizes & DRYs session/job ranges from kernelsmith
Minor fixes and status update

Minor tweaks after the PR from @kernelsmith

Remaining items:

1. Handle empty session IDs correctly, for example 'sessions -d' or 'sessions -k'
2. Find a method of explaining the range options in the help text
3. Retest all changed code areas
4. Edit PR Summary to reflect changes to the scope
rolling back a change
Move db bundler group to metasploit-framework-db.gemspec

MSP-11578

This will allow Metasploit Pro to use the
metasploit-framework-db.gemspec to ensure it has the correct version of
gems that were previously only in metasploit-framework's Gemfile and so
weren't being checked for version compatibility when Pro used
metasploit-framework.gemspec.
Explicitly require 'metasploit/credential' and 'metasploit_data_models'

By putting the db group into the metasploit-framework-db.gemspec,
bundler no longer automatically required 'metasploit/credential' and
'metasploit_data_models' because gems, such as metasploit-framework-db,
are expected to explictly require their dependencies.
Move pcap bundler group to metasploit-framework-pcap.gemspec

MSP-11578

This will allow Metasploit Pro to use the
metasploit-framework-pcap.gemspec to ensure it has the correct version of
gems that were previously only in metasploit-framework's Gemfile and so
weren't being checked for version compatibility when Pro used
metasploit-framework.gemspec.
Add metasploit-framework as dependency of metasploit-framework-pcap

MSP-11578

Any of the optional depenency gems should depend on the minimal
metasploit-framework as it supplies the versioning information.
Update Gemfile.lock

MSP-11578