Fixing bugs in SEQUENCE, part 3

This is a list smaller bugs for SEQUENCE's that should be fixed before 10.3.1. A lot of the following things where reported by Peter Gulutzan.

Bugs and missing features

• SET @x = PREVIOUS VALUE FOR x;
  > Result = Error 1146 (42S02) Table 'test.x' doesn't exist
  Should be SEQUENCE doesn't exists

• CREATE SEQUENCE x START WITH 1 INCREMENT BY 123456789012345678;
  > Result = Error 4061 (HY000) Sequence 'test.x' values are conflicting
  > This is not a helpful message, saying "too big number" would be better.

• Create better error messages for the test of initial seqeunce values in:
  bool sequence_definition::check_and_adjust(bool set_reserved_until)
  But try to create reusable error messages
  Type:
  %s must be less than %s
  Too big value for %s
  Add also a check the cache can't be < 0 and not equal or bigger than
  LONGLONG_MAX.

• This should give an error for the second create:
  CREATE TEMPORARY TABLE s1 (s1 INT);
  CREATE TEMPORARY SEQUENCE s1 (s1 INT);

• CREATE TABLE s1 (s1 INT);
  DROP SEQUENCE s1;
  > Error 4066 (42S02) 'test.s1' is not a SEQUENCE
  CREATE TEMPORARY TABLE s1 (s1 INT);
  DROP TEMPORARY SEQUENCE s1;
  > Error 4067 (42S02) Unknown SEQUENCE: 'test.s1'

The second DROP should also give error 4066

• create trigger s1 before update on sequence_name for each row set @a = 5;
  The above should fail with a new error 'One can't create a trigger on
  a sequence"