Modify the Rake compile task to exclude native:

- I know it feels kind of a weird change as we only perform native
  compilation on CI.

  The issue is that RakeCompiler wasn't really meant to build fat gems
  for native compilation. Native compilation with Rake Compiler was
  meant for development purposes to compile the project and test it.

  When the compilation kicks in, we build `3.1/foo.so` `3.2/foo.so`
  but we also end up with a `foo.so` that gets compiled at
  `lib/foo.so`.

  The workaround we do to make Rake Compiler build fat gems natively
  is hacking it by pretending we are doing cross platform compilation
  using `ext.platform = [RUBY_PLATFORM]`.

Author: Edouard-chin

lib/cibuildgem/compilation_tasks.rb

@@ -60,6 +60,7 @@ def define_task(path, binary_name)
         ext.gem_spec = gemspec
         ext.cross_platform = normalized_platform
         ext.cross_compile = true
+        ext.no_native = true
       end
 
       disable_shared unless Gem.win_platform?

lib/cibuildgem/tasks/wrapper.rake

@@ -5,10 +5,6 @@ require_relative "../compilation_tasks"
 task = Cibuildgem::CompilationTasks.new(!Rake::Task.task_defined?(:gem))
 
 task "cibuildgem:setup" do
-  Rake.application.instance_variable_get(:@tasks).delete_if do |name, _|
-    name == "native:#{task.gemspec.name}:#{task.normalized_platform}"
-  end
-
   task.setup
 end