You should consider to store your data in a normalized schema. In your case the table should look like:
| id | k |        v |
|----|---|----------|
|  1 | A |       10 |
|  1 | B |       20 |
|  1 | C |       30 |
|  2 | A | Positive |
|  2 | B | Negative |
This schema is more flexible and you will see why.
So how to convert the given data into the new schema? You will need a helper table containing sequence numbers. Since your column is varchar(255) you can only store 128 values (+ 127 delimiters) in it. But let's just create 1000 numbers. You can use any table with enough rows. But since any MySQL server has the information_schema.columns table, I will use it.
drop table if exists helper_sequence;
create table helper_sequence (i int auto_increment primary key)
    select null as i
    from information_schema.columns c1
    join information_schema.columns c2
    limit 1000;
We will use this numbers as position of the values in your string by joining the two tables.
To extract a value from a delimited string you can use the substring_index() function. The value at position i will be
substring_index(substring_index(t.options, '|', i  ), '|', -1)
In your string you have a sequence of keys followed by its values. The position of a key is an odd number. So if the position of the key is i, the position of the corresponding value will be i+1
To get the number of the delimiters in the string and limit our join we can use
char_length(t.options) - char_length(replace(t.options, '|', ''))
The query to store the data in a normalized form would be:
create table normalized_table
    select t.id
        , substring_index(substring_index(t.options, '|', i  ), '|', -1) as k
        , substring_index(substring_index(t.options, '|', i+1), '|', -1) as v
    from old_table t
    join helper_sequence s
      on s.i <= char_length(t.options) - char_length(replace(t.options, '|', ''))
    where s.i % 2 = 1
Now run select * from normalized_table and you will get this:
| id | k |        v |
|----|---|----------|
|  1 | A |       10 |
|  1 | B |       20 |
|  1 | C |       30 |
|  2 | A | Positive |
|  2 | B | Negative |
So why is this format a better choice? Besides many other reasons, one is that you can easily convert it to your old schema with
select id, group_concat(concat(k, '|', v) order by k separator '|') as options
from normalized_table
group by id;
| id |               options |
|----|-----------------------|
|  1 |        A|10|B|20|C|30 |
|  2 | A|Positive|B|Negative |
or to your desired format
select id, group_concat(concat(k, '|', v) order by k separator ',') as options
from normalized_table
group by id;
| id |               options |
|----|-----------------------|
|  1 |        A|10,B|20,C|30 |
|  2 | A|Positive,B|Negative |
If you don't care about normalization and just want this task to be done, you can update your table with
update old_table o
join (
    select id, group_concat(concat(k, '|', v) order by k separator ',') as options
    from normalized_table
    group by id
) n using (id)
set o.options = n.options;
And drop the normalized_table.
But then you won't be able to use simple queries like
select *
from normalized_table
where k = 'A'
See demo at rextester.com