Add labels to the achievement admonitions.

profiler/src/achievements/100Million.md

@@ -7,6 +7,8 @@ Capturing a long-running profile trace is easy. Need to profile an hour of your
 Note that it doesn't make much sense to instrument every little function you might have. The cost of the instrumentation itself will be higher than the cost of the function in such a case.
 
 > [!TIP]
+> **Tip**
+>
 > Keep in mind that the more zones you have, the more memory and CPU time the profiler will use. Be careful not to run out of memory.
 >
 > To capture 100 million zones, you will need approximately 4 GB of RAM.

profiler/src/achievements/InstrumentationIntro.md

@@ -17,6 +17,8 @@ void SomeFunction()
 Now, when you profile your application, you will see a new zone appear on the timeline for each call to the function. This allows you to see how much time is spent in each call and how many times the function is called.
 
 > [!NOTE]
+> **Note**
+>
 > The `ZoneScoped` macro is just one of the many macros provided by Tracy. See the documentation for more information.
 
 The above description applies to C++ code, but things are done similarly in other programming languages. Refer to the documentation for your language for more information.

profiler/src/achievements/SamplingIntro.md

@@ -7,4 +7,6 @@ While instrumentation requires changes to your code, sampling does not. However,
 Sampling is automatic on Linux. On Windows, you must run the profiled application as an administrator for it to work.
 
 > [!WARNING]
+> **Warning**
+>
 > Depending on your system configuration, some additional steps may be required. Please refer to the user manual for more information.