chore: enable data-pipeline feature in shipped artifacts

[ganeshnj]

What does this PR do?

With this change, we will start shipping the data-pipeline code in the shipped artifacts.

I also made some refactor to make it easier to make such changes in future so we don't make mistake like cbindgen,datadog-profiling-ffi/ddtelemetry-ffi was included multiple times in past at

libdatadog/build-profiling-ffi.sh

Line 141 in c6ad4ff

FEATURES="--features crashtracker-collector,crashtracker-receiver,cbindgen,datadog-profiling-ffi/ddtelemetry-ffi,cbindgen,datadog-profiling-ffi/ddtelemetry-ffi,datadog-profiling-ffi/demangler,symbolizer"

Motivation

data-pipeline integration in .NET SDK requires data-pipeline stuff as per DataDog/dd-trace-dotnet#6314, hence we need to start shipping the code so integrations can use it

How to test the change?

on mac

❯ ./build-profiling-ffi.sh bin
<truncated>
Building for features: cbindgen,crashtracker-collector,crashtracker-receiver,data-pipeline-ffi,datadog-profiling-ffi/ddtelemetry-ffi,datadog-profiling-ffi/demangler
<truncated>
[ 50%] Building C object CMakeFiles/libdatadog-crashtracking-receiver.dir/libdatadog-crashtracking-receiver.c.o
[100%] Linking C executable libdatadog-crashtracking-receiver
ld: warning: ignoring duplicate libraries: '-lSystem', '-liconv'
[100%] Built target libdatadog-crashtracking-receiver
Done.

on windows

❯ .\windows\build-artifacts.ps1 bin
<truncated>
Building for features: data-pipeline-ffi,datadog-profiling-ffi/crashtracker-collector,datadog-profiling-ffi/crashtracker-receiver,datadog-profiling-ffi/ddtelemetry-ffi,datadog-profiling-ffi/demangler
<truncated>
WARN: Missing `[defines]` entry for `feature = "receiver"` in cbindgen config.
WARN: Missing `[defines]` entry for `unix` in cbindgen config.
WARN: Missing `[defines]` entry for `feature = "receiver"` in cbindgen config.
Build finished

[gleocadie]

LGTM

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.55%. Comparing base (c6ad4ff) to head (1200d9c).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #751      +/-   ##
==========================================
- Coverage   70.59%   70.55%   -0.04%     
==========================================
  Files         296      296              
  Lines       43246    43246              
==========================================
- Hits        30528    30512      -16     
- Misses      12718    12734      +16     

Components	Coverage Δ
crashtracker	37.14% <ø> (ø)
crashtracker-ffi	8.67% <ø> (ø)
datadog-alloc	98.73% <ø> (ø)
data-pipeline	91.98% <ø> (ø)
data-pipeline-ffi	0.00% <ø> (ø)
ddcommon	83.46% <ø> (ø)
ddcommon-ffi	69.12% <ø> (ø)
ddtelemetry	59.05% <ø> (ø)
ddtelemetry-ffi	22.13% <ø> (ø)
dogstatsd	89.45% <ø> (ø)
dogstatsd-client	79.77% <ø> (ø)
ipc	82.86% <ø> (+0.10%)	⬆️
profiling	84.30% <ø> (ø)
profiling-ffi	77.46% <ø> (ø)
serverless	0.00% <ø> (ø)
sidecar	38.01% <ø> (ø)
sidecar-ffi	0.00% <ø> (ø)
spawn-worker	50.36% <ø> (ø)
tinybytes	94.77% <ø> (ø)
trace-mini-agent	72.36% <ø> (ø)
trace-normalization	98.23% <ø> (ø)
trace-obfuscation	95.77% <ø> (ø)
trace-protobuf	77.67% <ø> (ø)
trace-utils	93.54% <ø> (ø)

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[ekump]

.NET build artifacts are not my area of expertise, but LGTM

[gleocadie]

.NET build artifacts are not my area of expertise, but LGTM

I'm here for that ;)