Merge the docs folder into readme (#259)

* Merge the docs folder into readme

Signed-off-by: KP Choi <kp5.choi@samsung.com>

* Drop the profile numbering convention description

Signed-off-by: KP Choi <kp5.choi@samsung.com>

---------

Signed-off-by: KP Choi <kp5.choi@samsung.com>

Author: kpchoi

README.md

@@ -14,7 +14,7 @@ The OpenAPV supports the following features:
 - RGB content coding with the 444 profiles through color description signalling
 - Constant QP (CQP) and average bitrate (ABR) rate control algorithms
 - [APV Family](/readme/apv_family.md) configurations for typical target bitrate setting of encoder
-- [APV Profile Extensions](/docs/profile_ext.md) defined by the OpenAPV project on top of the RFC 9924 profiles
+- [APV Profile Extensions](/readme/profile_ext.md) defined by the OpenAPV project on top of the RFC 9924 profiles
 
 
 ## APV codec
@@ -106,7 +106,7 @@ Encoding:
     oapv_app_enc -i input_1920x1080_yuv422_10bit.yuv -w 1920 -h 1080 -d 10 -z 30 --input-csp 2 -o encoded.apv
     oapv_app_enc -i input.y4m -o encoded.apv
 
-Encoding RGB content (G/B/R planar order, coded as 444 with the identity matrix signalled in the color description; see the [Programmer's Guide](/docs/programmers_guide.md) for details):
+Encoding RGB content (G/B/R planar order, coded as 444 with the identity matrix signalled in the color description; see the [Programmer's Guide](/readme/programmers_guide.md) for details):
 
     oapv_app_enc -i input_rgb_gbr_planar_10bit.yuv -w 1920 -h 1080 -d 10 -z 30 --input-csp 3 --profile 444-10 --color-primaries 1 --color-transfer 13 --color-matrix 0 --color-range 1 -o encoded.apv
 
@@ -124,7 +124,7 @@ Decoding:
 
 ## Programmer's guide
 
-See the [Programmer's Guide](/docs/programmers_guide.md) for how to write
+See the [Programmer's Guide](/readme/programmers_guide.md) for how to write
 encoding and decoding code with the library, including PBU-based decoding,
 tile-based partial decoding, runtime configuration, RGB content encoding,
 and the custom memory allocator interface.

docs/profile_ext.md readme/profile_ext.mddocs/profile_ext.md renamed to readme/profile_ext.md

@@ -10,16 +10,6 @@ only be decoded by implementations that support the corresponding extension.
 For the profiles defined by RFC 9924 (422-10, 422-12, 444-10, 444-12,
 4444-10, 4444-12, and 400-10), see [Section 9.3 of the RFC](https://www.rfc-editor.org/rfc/rfc9924.html#section-9.3).
 
-## Numbering convention
-
-A profile which extends an RFC 9924 profile uses a `profile_idc` value one
-less than the next RFC 9924 profile, counting downward if more extensions of
-the same profile are added later. For example, the first extension of the
-422-10 profile (`profile_idc` 33) uses `profile_idc` 43, one less than the
-422-12 profile (`profile_idc` 44). Since the 400-10 profile (`profile_idc`
-99) is the last profile of RFC 9924, its extensions count down from 109, one
-less than 110, the next value in the RFC 9924 numbering pattern.
-
 ## Defined extension profiles
 
 | Profile          | profile_idc | chroma_format_idc | bit_depth_minus8 | Description                        |
@@ -34,9 +24,6 @@ less than 110, the next value in the RFC 9924 numbering pattern.
 | 444-16C12        | 140         | 3                 | 4                | 16-bit source companded to 12-bit  |
 | 4444-16C12       | 144         | 3 or 4            | 4                | 16-bit source companded to 12-bit  |
 
-Note: 444-16C12 and 4444-16C12 predate the numbering convention above and
-keep their original `profile_idc` values.
-
 ## UNCONST profiles
 
 The UNCONST profiles relax conformance constraints of the corresponding