test ber encoding of message_id > 128
Fix BER encoding test fixture for int value 128
Try padding based on most significant bit
Pad based on most significant bit in octet

Was just looking at most significant bit.
Fix the expected encoded value for 255
Add negative reference encoded values, but disable
Fix expected encoded integers

Makes the format consistent (hex), and updated based on various sample sources.
Add roundtrip encoding/decoding tests for samples
Fix negative Fixnum encoding
Fix negative integer decoding
Spelling correction
Consolidate Fixnum, Bignum ext into Integer
Expand negative test samples
remove unused integration test
Merge pull request #173 from ruby-ldap/ber-encoding-integers-refactoring

Refactor BER encoding/decoding of Integers
Merge pull request #172 from ruby-ldap/ber-message-id-encoding-fix

Test ber encoding of message_id > 128