Yes, it's possible.

The contract expects the "object" value of the "bytecode" structure provided by Remix. Currently, when you click to copy the "bytecode" from Remix, you end up with a structure that looks like this:

bytecode = {
  'linkReferences':[],
  'object': '6080604052336000806...',
  'opcodes': 'PUSH1 0x80...',
  'sourcemap': '50:1984:0:-;;;2...'
}

The Contract is expecting only the "object" value to be provided to it as the bytecode argument.

I figured out the answer to my own question. Yes, it's possible.

The contract expects only the "object" value of the "bytecode" structure provided by Remix. Currently, when you click to copy the "bytecode" from Remix, you end up with a structure that looks like this:

bytecode = {
  'linkReferences':[],
  'object': '6080604052336000806...',
  'opcodes': 'PUSH1 0x80...',
  'sourcemap': '50:1984:0:-;;;2...'
}

I was passing this whole structure as the bytecode argument, which is wrong. The contract is only expecting the "object" value.

Currently, the "bytecode" that Remix provides is in a structure like this:

{
  'linkReferences':[],
  'object': '6080604052336000806...',
  'opcodes': 'PUSH1 0x80...',
  'sourcemap': '50:1984:0:-;;;2...'
}

The "bin/bytecode" that the Contract is expecting is the "object" value of the above structure.

Yes, it's possible.

The contract expects the "object" value of the "bytecode" structure provided by Remix. Currently, when you click to copy the "bytecode" from Remix, you end up with a structure that looks like this:

bytecode = {
  'linkReferences':[],
  'object': '6080604052336000806...',
  'opcodes': 'PUSH1 0x80...',
  'sourcemap': '50:1984:0:-;;;2...'
}

The Contract is expecting only the "object" value to be provided to it as the bytecode argument.