feat(runtime-core): unwrap nested refs on the component

[pikax]

The commit 6b10f0c broke the auto-unwrap when the reference is in the middle of the object, added tests to cover some more cases.

  it('should expose return values to template render context', () => {
    const Comp = defineComponent({
      setup() {
        return {
          // ref should auto-unwrap
          ref: ref('foo'),
          // object exposed as-is
          object: reactive({ msg: 'bar' }),
          // primitive value exposed as-is
          value: 'baz',
          // nested ref at the end should auto-unwrap
          nested: { ref: ref('qux') },
          // ref with nested should auto-unwrap
          refNested: ref({
            nested: {
              ref: ref('foo')
            }
          }),
          // nested ref in the middle should auto-unwrap
          refMiddleNested: {
            nested: ref({
              msg: 'bar'
            })
          }
        }
      },
      render() {
        return `${this.ref} ${this.object.msg} ${this.value} ${
          this.nested.ref
        } ${this.refNested.nested.ref} ${this.refMiddleNested.nested.msg}`
      }
    })
    expect(renderToString(h(Comp))).toMatch(`foo bar baz qux foo bar`)
  })

[pikax]

@yyx990803 Just read the commit message from the commit I mentioned... Making this PR invalid, but also making the typescript typings (unwrapped ) invalid also.

On the example above the correct access to the properties is:

`${this.ref} ${this.object.msg} ${this.value} ${this.nested.ref.value} ${this.refNested.nested.ref} ${this.refMiddleNested.nested.value.msg}`

But the current recursive unwrap, makes the typescript throwing an error on that. The documentation is also misleading, it should be updated to reflect the new behaviour.

[yyx990803]

FYI this behavior will be reverted in the next release (back to implicit deep unwrap)