Rename PERFETTO_EXPORT to PERFETTO_COMPONENT_EXPORT

We already have different export macros, and a future CL is going to
introduce a different one.

This rename tries to make it clearer that the PERFETTO_EXPORT macro is
only used for component builds.

Change-Id: Iad322496afb4560f42f81dbb5662a48cd384dd91

docs/design-docs/api-and-abi.md

diff --git a/docs/design-docs/api-and-abi.md b/docs/design-docs/api-and-abi.md
index 283cdf5..8e6a639 100644
--- a/docs/design-docs/api-and-abi.md
+++ b/docs/design-docs/api-and-abi.md
@@ -497,9 +497,10 @@
 different linker unit. It is fine to link AND use the client library within
 the same shared library, as long as none of the perfetto C++ API is exported.
 
-The `PERFETTO_EXPORT` annotations are only used when building the third tier of
-the client library in chromium component builds and cannot be easily repurposed
-for delineating shared library boundaries for the other two API tiers.
+The `PERFETTO_COMPONENT_EXPORT` annotations are only used when building the
+third tier of the client library in chromium component builds and cannot be
+easily repurposed for delineating shared library boundaries for the other two
+API tiers.
 
 This is because the C++ the first two tiers of the Client Library C++ API make
 extensive use of inline headers and C++ templates, in order to allow the